Closed strogdon closed 7 years ago
OK, that is an issue with the m4 macro for finding boost. It is behaving in an unusual fashion but then boost is an unusual beast.
Apparently brial-1.0.0
was OK unless it picked up on the host boost
and the lower version number was adequate.
That's very odd, I cannot think of a recent change in boost detection from that version. But the macro needs tuning, the newest version may be better, still figuring it out.
It is a really terrible macro but I think I know what to do. Can you add
--with-boost="${EPREFIX}"/usr
to econf
in the ebuild and see if that fix the detection.
Yes, that fixed the configure and build. I now have to figure out why gcc 6.3.0
stuff is being linked when gcc 6.4.0
is being used
ldd -r ~/usr/lib/libbrial_groebner.so
linux-vdso.so.1 (0x00007ffc85bf2000)
libbrial.so.1 => /storage/strogdon/gentoo-rap/usr/lib64/libbrial.so.1 (0x00007fdd5a84e000)
libpng16.so.16 => /storage/strogdon/gentoo-rap/usr/lib64/libpng16.so.16 (0x00007fdd5a607000)
libz.so.1 => /storage/strogdon/gentoo-rap/usr/lib64/libz.so.1 (0x00007fdd5a3ea000)
libm4ri-0.0.20140914.so => /storage/strogdon/gentoo-rap/usr/lib64/libm4ri-0.0.20140914.so (0x00007fdd5a1b7000)
libstdc++.so.6 => /storage/strogdon/gentoo-rap/usr/lib/gcc/x86_64-pc-linux-gnu/6.3.0/libstdc++.so.6 (0x00007fdd59dbc000)
libm.so.6 => /storage/strogdon/gentoo-rap/lib64/libm.so.6 (0x00007fdd59aa5000)
libc.so.6 => /storage/strogdon/gentoo-rap/lib64/libc.so.6 (0x00007fdd596f3000)
libgcc_s.so.1 => /storage/strogdon/gentoo-rap/usr/lib/gcc/x86_64-pc-linux-gnu/6.3.0/libgcc_s.so.1 (0x00007fdd594dc000)
libgomp.so.1 => /storage/strogdon/gentoo-rap/usr/lib/gcc/x86_64-pc-linux-gnu/6.3.0/libgomp.so.1 (0x00007fdd592af000)
libpthread.so.0 => /storage/strogdon/gentoo-rap/lib64/libpthread.so.0 (0x00007fdd5908f000)
/storage/strogdon/gentoo-rap/lib64/ld-linux-x86-64.so.2 (0x00007fdd5b1c3000)
libdl.so.2 => /storage/strogdon/gentoo-rap/lib64/libdl.so.2 (0x00007fdd58e8b000)
Looks like there is a buggy gcc-config
.
That bit is out of my hand, you may want to forward it to the gentoo-alt mailing list.
It suddenly strikes me that you don't have libgomp directly. You get it by loading libm4ri. If you do readelf -d
on the same library you shouldn't see libgomp in the list. On the other hand I would expect to see libstdc++ from gcc 6.4.0 but they will have the same soname.
Have you rebuilt m4ri with gcc 6.4.0?
Yes you are correct relative to readelf -d
and libgomp. Backported gcc-config
and everything seems OK. I had rebuild system and a host of other things before I homed in on gcc-config
.
ldd -r ~/usr/lib/libbrial_groebner.so
linux-vdso.so.1 (0x00007ffc61bb7000)
libbrial.so.1 => /storage/strogdon/gentoo-rap/usr/lib64/libbrial.so.1 (0x00007f8f02ffd000)
libpng16.so.16 => /storage/strogdon/gentoo-rap/usr/lib64/libpng16.so.16 (0x00007f8f02db6000)
libz.so.1 => /storage/strogdon/gentoo-rap/usr/lib64/libz.so.1 (0x00007f8f02b99000)
libm4ri-0.0.20140914.so => /storage/strogdon/gentoo-rap/usr/lib64/libm4ri-0.0.20140914.so (0x00007f8f02966000)
libstdc++.so.6 => /storage/strogdon/gentoo-rap/usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/libstdc++.so.6 (0x00007f8f02564000)
libm.so.6 => /storage/strogdon/gentoo-rap/lib64/libm.so.6 (0x00007f8f0224d000)
libc.so.6 => /storage/strogdon/gentoo-rap/lib64/libc.so.6 (0x00007f8f01e9b000)
libgcc_s.so.1 => /storage/strogdon/gentoo-rap/usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/libgcc_s.so.1 (0x00007f8f01c84000)
libgomp.so.1 => /storage/strogdon/gentoo-rap/usr/lib/gcc/x86_64-pc-linux-gnu/6.4.0/libgomp.so.1 (0x00007f8f01a56000)
libpthread.so.0 => /storage/strogdon/gentoo-rap/lib64/libpthread.so.0 (0x00007f8f01836000)
/storage/strogdon/gentoo-rap/lib64/ld-linux-x86-64.so.2 (0x00007f8f03972000)
libdl.so.2 => /storage/strogdon/gentoo-rap/lib64/libdl.so.2 (0x00007f8f01632000)
I will close this one.
I have numerous new Prefix failures with
8.1.beta5
but before I address that I need to build the subjectbrial
. The failure fromconfig.log
:Apparently the configure is picking up on the host
boost
which is version1.49
. I have1.63
in Prefix. The need to rebuild (I have brial-1.0.0 installed) is that I've noticed linking withlibgomp
fromgcc-6.3
and things are being built withgcc-6.4
. Numerousmemory
errors and inability to startthreads
, ..., etc. But fixingbrial
is the first step, I hope.