armadillo @9.700.3_0+arpack+gcc9+superlu: armadillo is using libstdc++ (this installation is configured to use libc++)

[hugo-ribeiro (Hugo Ribeiro)]

I got this message

armadillo is using libstdc++ (this installation is configured to use libc++)
--->  Found 1 broken port, determining rebuild order
You can always run 'port rev-upgrade' again to fix errors.
The following ports will be rebuilt: armadillo @9.700.3+arpack+gcc9+superlu

after upgrading from 9.700.2 to 9.700.3. Macports tried to rebuild the port 3 times (with rev-upgrade), but the problem persists. I also tried to uninstall and reinstall armadillo, but to no avail. I've attached the output of port -d -y rev-upgrade.

[Schamschula (Marius Schamschula)]

This is strange. From your attachment I see you are on Mojave.

Before committing I built the update under Mojave, w/o any errors.

Which version of Xcode do you have installed?

[hugo-ribeiro (Hugo Ribeiro)]

I have Xcode 10.3 installed. Here's the output of xcodebuild -version

Xcode 10.3
Build version 10G8

and the output of /usr/bin/gcc --version

configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/usr/include/c++/4.2.1
Apple LLVM version 10.0.1 (clang-1001.0.46.4)
Target: x86_64-apple-darwin18.7.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

and the output from /usr/bin/clang --version

Apple LLVM version 10.0.1 (clang-1001.0.46.4)
Target: x86_64-apple-darwin18.7.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

Finally, since I am using the +gcc9 variant, here is the output of gcc -v

Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/opt/local/libexec/gcc/x86_64-apple-darwin18/9.2.0/lto-wrapper
Target: x86_64-apple-darwin18
Configured with: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc9/gcc9/work/gcc-9.2.0/configure --prefix=/opt/local --build=x86_64-apple-darwin18 --enable-languages=c,c++,objc,obj-c++,lto,fortran --libdir=/opt/local/lib/gcc9 --includedir=/opt/local/include/gcc9 --infodir=/opt/local/share/info --mandir=/opt/local/share/man --datarootdir=/opt/local/share/gcc-9 --with-local-prefix=/opt/local --with-system-zlib --disable-nls --program-suffix=-mp-9 --with-gxx-include-dir=/opt/local/include/gcc9/c++/ --with-gmp=/opt/local --with-mpfr=/opt/local --with-mpc=/opt/local --with-isl=/opt/local --enable-stage1-checking --disable-multilib --enable-lto --enable-libstdcxx-time --with-build-config=bootstrap-debug --with-as=/opt/local/bin/as --with-ld=/opt/local/bin/ld --with-ar=/opt/local/bin/ar --with-bugurl=https://trac.macports.org/newticket --disable-tls --with-pkgversion='MacPorts gcc9 9.2.0_0' --with-sysroot=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk
Thread model: posix
gcc version 9.2.0 (MacPorts gcc9 9.2.0_0)

[Schamschula (Marius Schamschula)]

Indeed, it is the +gcc9 variant (and perhaps other gcc variants) that is causing the issue.

I can reproduce your results.

[Schamschula (Marius Schamschula)]

This looks like an old issue has resurfaced: #56554

[Schamschula (Marius Schamschula)]

I'm going to push a workaround, but this seems to be an issue with MacPorts 2.6.x.

[Schamschula (Marius Schamschula)]

In a1ad3c0cd85a266e1e0ad5319d473757d31ba388/macports-ports (master):

armadillo: fix libstdc++/libc++ mismatch

Closes: #59173