Performance issue of libtool-2.4.4
Hello libtool, It seems that libtool (2.4.4) has increased the packages build time, after a rough investigation, it maybe because new libtoolize needs run a m4 command: # Save the command pipeline results for further use by callers of # this function. func_extract_trace_result=`$ECHO $_G_mini \ |$M4 -daq --prefix $_G_m4_traces - $@ 21 1/dev/null \ |$SED -n -e $_G_transform` This may increase the build time (just a rough guess), does any other one also notice the performance issues, please ? I will go on investigating on it. Any suggestion is appreciated. -- Thanks Robert ___ https://lists.gnu.org/mailman/listinfo/libtool
Re: Performance issue of libtool-2.4.4
On Mon, 2 Feb 2015, Robert Yang wrote: Hello libtool, It seems that libtool (2.4.4) has increased the packages build time, after a rough investigation, it maybe because new libtoolize needs run a m4 command: Did you time 'libtoolize' and compare the timings with 2.4.4 to the release you were using before? Libtoolize is not normally considered to be part of package build time since packages usually already come 'libtoolized' (using some random version of libtool). Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer,http://www.GraphicsMagick.org/ ___ https://lists.gnu.org/mailman/listinfo/libtool
