Victor, as you ship libtool, you can just patch it, essentially as in https://lists.gnu.org/archive/html/libtool-patches/2013-11/msg00015.html It needs to be moved to a slightly different place, but it works, you'd get a properly linked libntl.so with the patch (attached), I checked this on Linux at least. HTH Dima
On Wed, Aug 28, 2019 at 4:55 PM Antonio Rojas <nqn7...@gmail.com> wrote: > > > > El miércoles, 28 de agosto de 2019, 15:15:18 (UTC+2), Victor Shoup escribió: >> >> 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. >> > > I'd say the easiest fix would be to treat libpthread just like any other > library and link to it by passing -lpthread to the linker instead of relying > on the -pthread gcc flag (I don't speak perl so I can't help with a patch, > sorry) > > -- > 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/e48173fb-ec1f-4e69-af58-19dc6035b32d%40googlegroups.com. -- 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/CAAWYfq2NWxGnhDGFj2g6-xfZ%2Bhfy%2BWKkaFcJyDnMNez3FGchsw%40mail.gmail.com.
ltmain.sh.diff
Description: Binary data
