bug-libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#9257: configure errors after upgrade to libtool 2.4


From: Julien ÉLIE
Subject: bug#9257: configure errors after upgrade to libtool 2.4
Date: Sat, 06 Aug 2011 21:48:42 +0200
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; fr; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11

Hi,

I am trying to upgrade the libtool 2.2.6b shipped with INN to libtool 2.4.
Unfortunately, I do not manage to make it work.

It appears that AC_OUTPUT, at the end of configure.ac, generates something
that is not understood when run.


Here is the commit that broke INN's configure:
    http://inn.eyrie.org/trac/changeset/9308

It is only an update from libtool 2.2.6b to 2.4.


Here are log files from an attempt to configure INN:
    http://iulius.dinauz.org/libtool-inn/


You will see at the end of output.console:



checking for Unix domain sockets... yes
checking log facility for news... LOG_NEWS
configure: creating ./config.status
Usage: /bin/sed [OPTION]... {script-only-if-no-other-script} [input-file]...
[...]
./configure: line 20068: /bin/sed -e 1s/^X//: No such file or directory
./configure: line 20068: : command not found
./configure: line 20068: : command not found
./configure: line 20068: : command not found
./configure: line 20068: : command not found
./configure: line 20068: : command not found
./configure: line 20068: : command not found
./configure: line 20068: : command not found
./configure: line 20068: : command not found
./configure: line 20068: i686-pc-linux-gnu: command not found
./configure: line 20068: linux-gnu: command not found
./configure: line 20068: : command not found
./configure: line 20068: i686-pc-linux-gnu: command not found
./configure: line 20068: linux-gnu: command not found
Usage: grep [OPTION]... PATTERN [FILE]...
Try `grep --help' for more information.
./configure: line 20068: /bin/grep -E: No such file or directory
./configure: line 20068: : command not found
./configure: line 20068: : command not found
[...]



Do you have any idea about what could trigger these errors?
How can they be fixed?

If you need other logs, do not hesitate to ask.


Thanks beforehand,

-- 
Julien ÉLIE

« La raison du plus fou est toujours la meilleure. » (Raymond Devos)





reply via email to

[Prev in Thread] Current Thread [Next in Thread]