[MacPorts] #70522: postgis3 violates MacPorts compiler setting
MacPorts
noreply at macports.org
Sat Aug 10 00:47:50 UTC 2024
#70522: postgis3 violates MacPorts compiler setting
---------------------------+--------------------
Reporter: barracuda156 | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.10.0
Resolution: | Keywords:
Port: postgis3 |
---------------------------+--------------------
Comment (by ryandesign):
Replying to [ticket:70522 barracuda156]:
> We have the same issue which we had with `pdal`:
Which issue was that?
> `compiler.thread_local_storage yes` should ensure Xcode gcc is avoided,
but it is not.
> {{{
> checking for gcc... ccache /opt/local/bin/gcc-mp-14
> }}}
`compiler.thread_local_storage yes` has successfully caused MacPorts to
select the newer gcc14 compiler.
> {{{
> checking for xcrun... /usr/bin/xcrun
> xcrun: error: unrecognized option: --show-sdk-version
>
> usage:
> xcrun [-verbose] [-no-cache] [-sdk <sdkroot>] [-log] [-run] <utility>
[argument ...]
> xcrun [-verbose] [-no-cache] [-sdk <sdkroot>] -find <utility>
> <tool> [tool arguments ...]
> ./configure: line 15491: test: =: unary operator expected
> }}}
Here it wasn't expecting a version of `xcrun` as old as you have. Not sure
what effect that will have on the build though I expect it only to affect
SDK selection, not compiler selection.
> {{{
> checking whether we are using the GNU C++ compiler... yes
> checking whether /usr/bin/gcc-4.2 -std=gnu99 accepts -g... yes
> checking how to run the C++ preprocessor... /usr/bin/gcc-4.2 -std=gnu99
-E
> checking for ld used by /usr/bin/gcc-4.2 -std=gnu99... /opt/local/bin/ld
> checking if the linker (/opt/local/bin/ld) is GNU ld... no
> checking whether the /usr/bin/gcc-4.2 -std=gnu99 linker
(/opt/local/bin/ld) supports shared libraries... yes
> checking for /usr/bin/gcc-4.2 -std=gnu99 option to produce PIC... -fno-
common -DPIC
> checking if /usr/bin/gcc-4.2 -std=gnu99 PIC flag -fno-common -DPIC
works... yes
> checking if /usr/bin/gcc-4.2 -std=gnu99 static flag -static works... no
> checking if /usr/bin/gcc-4.2 -std=gnu99 supports -c -o file.o... yes
> checking if /usr/bin/gcc-4.2 -std=gnu99 supports -c -o file.o...
(cached) yes
> checking whether the /usr/bin/gcc-4.2 -std=gnu99 linker
(/opt/local/bin/ld) supports shared libraries... yes
> checking dynamic linker characteristics... darwin10.0.0d2 dyld
> checking how to hardcode library paths into programs... immediate
> checking whether /usr/bin/gcc-4.2 -std=gnu99 supports C++11 features
with -std=c++11... no
> checking whether /usr/bin/gcc-4.2 -std=gnu99 supports C++11 features
with +std=c++11... no
> checking whether /usr/bin/gcc-4.2 -std=gnu99 supports C++11 features
with -h std=c++11... no
> checking whether /usr/bin/gcc-4.2 -std=gnu99 supports C++11 features
with -std=c++0x... no
> checking whether /usr/bin/gcc-4.2 -std=gnu99 supports C++11 features
with +std=c++0x... no
> checking whether /usr/bin/gcc-4.2 -std=gnu99 supports C++11 features
with -h std=c++0x... no
> configure: error: *** A compiler with support for C++11 language
features is required.
> }}}
Here something has gone wrong and it is not using the compiler MacPorts is
telling it to use.
> Also, C++11 must explicitly be set, otherwise needed flags are not
added.
According to #67476 it needs C++14.
--
Ticket URL: <https://trac.macports.org/ticket/70522#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list