Opened 14 months ago

Last modified 14 months ago

#63535 assigned defect

boost176 @1.76.0_2: fails to configure on Leopard i386: Could not find a suitable toolset.

Reported by: kencu (Ken) Owned by: michaelld (Michael Dickens)
Priority: Normal Milestone:
Component: ports Version:
Keywords: leopard Cc:
Port: boost176

Description

Leopard i386 is trying to build boost176 using clang-7.0, as it is configured to do, but this is no bueno:

:debug:configure CC='/opt/local/bin/clang-mp-7.0'
:debug:configure CC_PRINT_OPTIONS='YES'
:debug:configure CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_boost176/boost176/work/.CC_PRINT_OPTIONS'
:debug:configure CFLAGS='-pipe -Os -arch i386'
:debug:configure CPATH='/opt/local/include'
:debug:configure CPPFLAGS='-I/opt/local/include'
:debug:configure CXX='/opt/local/bin/clang++-mp-7.0'
:debug:configure CXXFLAGS='-pipe -Os -std=gnu++11 -stdlib=macports-libstdc++ -D_GLIBCXX_USE_CXX11_ABI=0 -arch i386'
:debug:configure DEVELOPER_DIR='/Developer'
:debug:configure F90FLAGS='-pipe -Os -m32'
:debug:configure FCFLAGS='-pipe -Os -m32'
:debug:configure FFLAGS='-pipe -Os -m32'
:debug:configure INSTALL='/usr/bin/install -c'
:debug:configure LDFLAGS='-L/opt/local/lib -Wl,-headerpad_max_install_names -arch i386'
:debug:configure LIBRARY_PATH='/opt/local/lib'
:debug:configure MACOSX_DEPLOYMENT_TARGET='10.5'
:debug:configure OBJC='/opt/local/bin/clang-mp-7.0'
:debug:configure OBJCFLAGS='-pipe -Os -arch i386'
:debug:configure OBJCXX='/opt/local/bin/clang++-mp-7.0'
:debug:configure OBJCXXFLAGS='-pipe -Os -std=gnu++11 -stdlib=macports-libstdc++ -D_GLIBCXX_USE_CXX11_ABI=0 -arch i386'
:debug:configure PATH='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_boost176/boost176/work/bin:/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin'
:info:configure Executing:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_boost176/boost176/work/boost_1_76_0" && ./bootstrap.sh --prefix=/opt/local --without-libraries=mpi --with-icu=/opt/local --without-libraries=context --without-libraries=coroutine --with-python=/opt/local/bin/python3.9 --with-python-root=/opt/local/bin/python3.9 
:debug:configure system:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_boost176/boost176/work/boost_1_76_0" && ./bootstrap.sh --prefix=/opt/local --without-libraries=mpi --with-icu=/opt/local --without-libraries=context --without-libraries=coroutine --with-python=/opt/local/bin/python3.9 --with-python-root=/opt/local/bin/python3.9 
:info:configure Could not find a suitable toolset.
:info:configure You can specify the toolset as the argument, i.e.:
:info:configure     ./build.sh [options] gcc
:info:configure Toolsets supported by this script are:
:info:configure     acc, clang, como, gcc, intel-darwin, intel-linux, kcc, kylix, mipspro,
:info:configure     pathscale, pgi, qcc, sun, sunpro, tru64cxx, vacpp

Attachments (1)

boost-176-fail-Leopard-i386.log (92.2 KB) - added by kencu (Ken) 14 months ago.

Download all attachments as: .zip

Change History (3)

Changed 14 months ago by kencu (Ken)

comment:1 Changed 14 months ago by kencu (Ken)

there is hope to have all the systems default to boost176 soon, but this is currently a blocker.

The obvious thing to try is forcing it to gcc7. If we do that, we should consider the situation where Leopard Intel is configured to use -stdlib=libc++ as realistically that is the right path for Leopard Intel to be taking if it wants to stay in the mixture longer-term here.

comment:2 Changed 14 months ago by kencu (Ken)

forcing Leopard Intel i386 to use gcc7 works (configured for cxxstdlib libstdc++, which is the default).

It will fail if Leopard i386 is configured for cxxstdlib libc++ however, which we should support. I guess we can special-case it.

I would prefer to see if we can get it to build with clang-7.0 always, but I'll take using gcc7 for libstdc++ and clang-7.0 for libc++ if we need to.

Last edited 14 months ago by kencu (Ken) (previous) (diff)
Note: See TracTickets for help on using tickets.