Bug 140345 - libtoolize creates invalid libtool files
libtoolize creates invalid libtool files
Product: Fedora
Classification: Fedora
Component: libtool (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Reed
Depends On:
  Show dependency treegraph
Reported: 2004-11-22 10:12 EST by Karsten Hopp
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-11-22 14:19:16 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Karsten Hopp 2004-11-22 10:12:26 EST
Description of problem:
assume that you have the following in your .spec file (see the latest gtk+):
libtoolize --force

When you now try to build the package, you'll end up with lots of errors like
../libtool: line 297: s,^.*/,,g: No such file or directory
../libtool: line 632: -e: command not found
*** Warning: inferring the mode of operation is deprecated.
*** Future versions of Libtool will require -mode=MODE be specified.
../libtool: line 926: -e: command not found
../libtool: line 926: -e: command not found
../libtool: line 926: -e: command not found
../libtool: line 926: -e: command not found
That's because SED isn't defined anywhere.
export SED=/bin/sed rpmbuild --rebuild ....  worked for me, but that's just a
workaround, not the solution.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. rpmbuild --rebuild gtk+-1.2.10-33.src.rpm
2. check the output
Comment 1 Daniel Reed 2004-11-22 14:19:16 EST
Automake 1.4 and Autoconf 2.13 are not supported or maintained, either upstream
or by Red Hat. One or both may be incompatible with modern Libtool. (I believe
Libtool 1.5.2 and beyond have had an explicit requirement on Autoconf 2.54 or

As both of these packages have been marked "deprecated", they may disappear at
any time. Please help the affected project migrate their build control files to
a form accepted by Automake 1.9 and Autoconf 2.59. If you can reproduce this
problem using Autoconf 2.59, please reopen. Thanks.

Note You need to log in before you can comment on or make changes to this bug.