Victor, as far as I understand the main configuration script of ntl
is the perl DoConfig script. It has nothing to do with libtool. libtool
is robust if you let it handle the configuration. It will not try to
fix a given one.
In a libtool configure.ac script you would just have a directive
AC_CHECK_LIB for pthread.
In short, I would suggest
3) Replace DoConfig by a configure.ac script
Vincent
Le 28/08/2019 à 15:15, Victor Shoup a écrit :
Thanks. I guess what I'm asking for is a solution. From what you say here,
and what is said in the links, the problem seems to be a bug in libtool,
not NTL. So a solution would be, either:
1) a patch other type of libtool workaround, or
2) an alternative to libtool.
I though the whole point of libtool was to take care of all this nonsense,
and if it's not doing that, then
it seems kind of pointless.
On Tuesday, August 27, 2019 at 1:42:51 PM UTC-4, Antonio Rojas wrote:
El martes, 27 de agosto de 2019, 16:25:12 (UTC+2), Victor Shoup escribió:
I reviewed some comments which mentioned a problem with ntl and threads.
I’m happy to fix that, but I don’t think I understand what the issue is.
Can anyone explain? Thanks.
Hi Victor,
IIRC I reported this to you about a year ago. The problem is that you are
using libtool as a build command, which calls the compiler with the
-nostdlib flag, which in turn overrides the -pthread flag, so the binaries
end up not being linked to libpthread. See eg. [1][2] for more info.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=661333
[2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25460
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-devel/fa916b1e-c62c-d64d-485e-a84b736a4bff%40gmail.com.
