Re: Makefile.in, LIBTOOL and shared/static builds.

2018-06-25 Thread or...@fredslev.dk
> I’m curious - it’s neat that slibtool exists, but if you need > functionality offered by libtool then why not just use libtool? Frankly libtool is 12,000+ line shell script which is hard to understand, maintain, fix and is rather slow. A while ago with my 6 core AMD FX-6350 cpu I tested buildin

Re: Makefile.in, LIBTOOL and shared/static builds.

2018-06-25 Thread Bob Friesenhahn
On Mon, 25 Jun 2018, or...@fredslev.dk wrote: I’m curious - it’s neat that slibtool exists, but if you need functionality offered by libtool then why not just use libtool? Frankly libtool is 12,000+ line shell script which is hard to understand, maintain, fix and is rather slow. Agreed. A

Re: Makefile.in, LIBTOOL and shared/static builds.

2018-06-25 Thread or...@fredslev.dk
> The overhead attributed to libtool seems rather high. Is there > something about your execution environment or your libtool usage which > causes more overhead than usual? Not that I am aware of, its the standard GNU libtool in Slackware64-current. > How does slibtool validate arguments? Does it