On 2020/01/22 18:25, Stefan Hagen wrote: > Stuart Henderson wrote: > > On 2020/01/21 18:22, Xiyue Deng wrote: > > > # C++14 required > > > -COMPILER= base-clang ports-clang > > > +COMPILER= base-clang ports-gcc > > > > This part is ok with me with the bump added. > > Experiement below: > > I don't have a gcc architecture available, so i tried to compile mail/mu > und its dependency database/xapian-core with COMPILER= ports-gcc set on > my amd64 box. > > It looks like xapian-core is not honoring the COMPILER= ports-gcc > flag.
That is working here, did you have an old package lying around etc?: $ objdump -p /pobj/xapian-core-1.4.14/fake-amd64/usr/local/lib/libxapian.so.5.1 | grep NEEDED NEEDED libz.so.5.0 NEEDED libuuid.so.14.0 NEEDED libestdc++.so.19.0 NEEDED libm.so.10.1 > Afterwards compiling and installing xapian-core, mail/mu still > complains about an incompatible ABI: > > ld: error: undefined symbol: > Xapian::Document::get_value[abi:cxx11](unsigned int) const No maildirs here for full tests with mu, but "make test" has lots of "OK"s.. > # nm --demangle: > mu-1.2.0/lib/tests/.libs/libxapian.so.5.1 > => _ZNK6Xapian8Document9get_valueEj > mu-1.2.0/lib/tests/.libs/libtestmucommon.a > => _ZNK6Xapian8Document9get_valueB5cxx11Ej > > I'm interested to find out why this is happening... > > Can this behavior break on other archs? > > Best Regards, > Stefan >
