FIXED : Re: libtool broken (was Re: Gcc broken. How to fix?)
Hi all,
The only way I could get libtool working again, was to install it from
source (bypassing dpkg) and then with that working libtool reinstallation
went fine.
This suggests that libtool is recursively dependant on itself. This can
be proved as follows:
root@dizzy > apt-get remove libtool
Reading Package Lists... Done
Building Dependency Tree... Done
The following packages will be REMOVED:
libtool
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 774kB will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 44369 files and directories currently installed.)
Removing libtool ...
root@dizzy > apt-get install libtool
Reading Package Lists... Done
Building Dependency Tree... Done
The following NEW packages will be installed:
libtool
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/177kB of archives. After unpacking 774kB will be used.
Selecting previously deselected package libtool.
(Reading database ... 44340 files and directories currently installed.)
Unpacking libtool (from .../libtool_1.3.3-9.1_all.deb) ...
Setting up libtool (1.3.3-9.1) ...
Configuring libtool...
Configuration name missing.
Usage: ./config.sub CPU-MFR-OPSYS
or ./config.sub ALIAS
where ALIAS is a recognized configuration type.
dpkg: error processing libtool (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
libtool
E: Sub-process /usr/bin/dpkg returned an error code (1)
I've submitted a bug report requesting that libtool needs to fixed so
that it can be removed and re-installed safely.
Erik
--
+----------------------------------------------------------+
Erik de Castro Lopo nospam@mega-nerd.com (Yes its valid)
+----------------------------------------------------------+
"If dolphins are so smart, why do they live in igloos?" -Eric Cartman
Reply to: