Thank you to Julian Ospald (hasufell) for bringing this to the tree so I can remove it from the sage-on-gentoo overlay. I notice however that Julian missed a problem we had fixed in the overlay: mkdir -p build/interfaces/test if [ "1" -eq "1" ]; then \ make build/interfaces/test/t-NTL-interface; \ build/interfaces/test/t-NTL-interface; \ fi make[1]: Entering directory `/scratch/portage/sci-mathematics/flint-2.4.3/work/flint-2.4.3' x86_64-pc-linux-gnu-g++ -O1 -march=native -pipe -ggdb -DFLINT_CPIMPORT=\"/usr/share/flint/CPimport.txt\" -I/scratch/portage/sci-mathematics/flint-2.4.3/work/flint-2.4.3 -I/usr/include -I/usr/include -I/usr/include interfaces/test/t-NTL-interface.cpp build/interfaces/NTL-interface.o -o build/interfaces/test/t-NTL-interface -L/scratch/portage/sci-mathematics/flint-2.4.3/work/flint-2.4.3 -L/usr/lib -L/usr/lib -L/usr/lib -lflint -lpthread -lmpfr -lgmp -lm -lntl ; x86_64-pc-linux-gnu-g++: error: build/interfaces/NTL-interface.o: No such file or directory make[1]: *** [build/interfaces/test/t-NTL-interface] Error 1 Could someone be so kind to apply the patch at the following URL: https://raw.githubusercontent.com/cschwan/sage-on-gentoo/2cf1e8adcfe8a7ea575b2b0a2b6bfa653800fbb3/sci-mathematics/flint/files/flint-2.4.3-makefile.patch to fix it. I haven't checked if the new gc useflag introduce similar problem or not but I wouldn't be surprised :) And while I am at it, I have tested this on x64-macos and is known to work on *-macos in the wider sage-on-gentoo community. Reproducible: Always Steps to Reproduce: 1. USE=ntl ebuild /usr/portage/sci-mathematics/flint/flint-2.4.4.ebuild test 2. 3.
(In reply to Francois Bissey from comment #0) > I notice however that Julian missed a problem we had fixed in the overlay: Has it been reported upstream?
+ 02 Jul 2014; Julian Ospald <hasufell@gentoo.org> flint-2.4.4.ebuild, + +files/flint-2.4.4-test.patch: + fix NTL test build wrt #516028
No. The story on why it hasn't is that you can't reproduce it on a vanilla build or one made inside sage. That puzzled me for some time but I think I finally worked out what is happening (after your prompting about upstream really). By default as delivered by upstream flint build both static and shared libraries and objects. So in a vanilla version of flint you have both .lo and .o objects around and this is not an issue. In Gentoo by default we turn off the static part of the build, exit the .o file. Upstream may be willing to switch the ntl test to .lo, an educated guess right now without looking at the code is that the rest of the tests are using .lo - that or the ntl test is different from the rest.
