On Mon, 7 Feb 2005, Hans Zaunere wrote:
My system build environment (Fedora Core 2, updated) has the following:
ltmain.sh (GNU libtool) 1.5.6 (1.1220.2.95 2004/04/11 05:50:42) autoconf (GNU Autoconf) 2.59 automake (GNU automake) 1.8.3
This had worked a few months ago, when we first started on this stuff.
So it seems that the libtool version required, won't work for x86_64, and more libtool/auto* voodoo :)
I fixed our build system (someone might think I broke it though :) so that
we really use only and only the libtool version we've bundled.
I think we should bundle libtool 1.5.10 in HEAD, but there are some issues
I need to fix before that happens. One of them is the requirement for autoconf 2.5x..
I am still quite skeptical of this bundled libtool idea. It is currently broken even on mainstream systems such as Debian x86 where do to the crappy packaging it is really important that people can build their own. See http://lerdorf.com/php/libtool.txt for a ./buildconf && ./configure run on a current 4.3.11-dev on a Debian x86 box. The last thing I want to do is start debugging libtool, but here is line 4096 from the generated libtool which throws so many errors:
4091 for obj in $save_libobjs
4092 do
4093 eval test_cmds=\"$reload_cmds $objlist $last_robj\"
4094 if test "X$objlist" = X ||
4095 { len=`expr "X$test_cmds" : ".*"` &&
4096 test "$len" -le "$max_cmd_len"; }; then
4097 objlist="$objlist $obj"And just before that it also had a problem with a $max_cmd_len related test:
4061 if test "X$skipped_export" != "X:" && len=`expr "X$test_cmds" : ".*"` &&
4062 test "$len" -le "$max_cmd_len" || test "$max_cmd_len" -le -1; then
4063 :
4064 else
Looking through it I don't see where $max_cmd_len is set. In my /usr/bin/libtool it has:
# What is the maximum length of a command? max_cmd_len=32768
near the top. Our generated one doesn't have that, so it appears ours is 0 which causes this chaos where it gets into some infinite loop where it sits and creates stuff in .libs forever. I had to ^C out of it and you can see the resulting files it creates in .libs in my output.
Simply doing a cp /usr/bin/libtool . and re-running make fixes it and the resulting binary works fine.
This may be fixable, but aren't the chances better that the native libtool will work on the native machine?
-Rasmus
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
