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

libtool broken (was Re: Gcc broken. How to fix?)



matthschulz wrote:
> 
> What about removing libtool with --force and then installing it back?

Nope. No change.

root@dizzy > dpkg --purge libtool
(Reading database ... 44436 files and directories currently installed.)
Removing libtool ...
dpkg - warning: while removing libtool, directory `/usr/share/libtool' not empty so not removed.

root@dizzy > ls /usr/share/libtool
total 8
drwxr-xr-x    2 root     root         4096 Jan  4 18:09 .
drwxr-xr-x   83 root     root         4096 Jan  4 05:57 ..
-rw-r--r--    1 root     root            0 Jan  4 18:06 config.log

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 ... 44407 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)


Erik
-- 
+----------------------------------------------------------+
  Erik de Castro Lopo  nospam@mega-nerd.com (Yes its valid)
+----------------------------------------------------------+
"I think there is a world market for maybe five computers." 
 -- Thomas Watson, Chairman of IBM, 1943



Reply to: