On Thu, Aug 29, 2019 at 5:13 PM Victor Shoup <sh...@cs.nyu.edu> wrote: > > Thanks for all of the thoughtful replies. > > I don't have time to rewrite the config script any time soon. > According to the libtool documentation, it is supposed to be usable > without relying on automake. > NTL's config script allows you to override the default libtool with a system > libtool, > so that seems like the simplest way to deal with this for now.
I must say I didn't verify that in my experiment the bundled libtool was used (I thought it's the default, but I don't know). If it's not the case then on the Debian 10 (buster) system I tried running this, the system libtool is already fixed in some way to fix that `-pthread` issue. (and not that the patch I provided actually does the job) Dima > > If I rewrite any of NTL's config scripts, it will likely be to move it over > to cmake. > > > On Thursday, August 29, 2019 at 3:43:33 AM UTC-4, Antonio Rojas wrote: >> >> >> >> El jueves, 29 de agosto de 2019, 0:06:49 (UTC+2), Dima Pasechnik escribió: >>> >>> >>> > Relying on patched bundled copies of dependencies is very much frowned >>> > upon by distros. It would be much preferable to make this work with >>> > unmodified libtool, which may be provided by the distribution. >>> >>> Well, libtool is just a shell script, more or less. NTL isn't unique >>> in shipping its own version. >>> Does Arch use its own libtool when building NTL, or the bundled one? >>> >> >> Regardless of how simple if may be, bundling dependencies increases the risk >> of introducing bugs and inconsistencies between distro packages. On Arch we >> are building ntl using system's libtool. >> Anyway, whatever solution is adopted is not such a big deal since there is >> an easy workaround (pass LDLIBS='-lpthread' to configure) that distros can >> keep using - It would just be nicer to fix it without resorting to patched >> dependencies IMO. > > -- > 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/43feca19-aecc-42f4-a8a3-0e15472ada37%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/CAAWYfq1Ggj850%3D6A7iTX2rUogX%2BmAxtHCuMSi4ijcjNjh6Bvvg%40mail.gmail.com.
