GNU bug report logs - #9257
configure errors after upgrade to libtool 2.4

Previous Next

To reply to this bug, email your comments to 9257 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Julien ÉLIE <julien <at> trigofacile.com>
To: bug-libtool <at> gnu.org
Subject: configure errors after upgrade to libtool 2.4
Date: Sat, 06 Aug 2011 21:48:42 +0200

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)

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.