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

Re: Gcc broken. How to fix?



matthschulz wrote:
> 
> Say dpkg -i _package-name_
> 
> Replace _package-name_ with the full name of the .deb file.
> 

Its not that simple. Have another look at the output below. The 
libtool package is installed its just thats its failing during 
configuration.

Thanks anyway for the help.

Erik

> Matth
> 
> On Mittwoch,  3. Januar 2001 14:02, Erik de Castro Lopo wrote:
> > Hi all,
> >
> > I had a crash on my laptop (battery died) which has left
> > me with a broken GCC.
> >
> > I tried uninstalling and reinstalling task-c-dev but now
> > I get the following:
> >
> >   root@dizzy > apt-get install task-c-dev
> >   Reading Package Lists... Done
> >   Building Dependency Tree... Done
> >   Sorry, task-c-dev is already the newest version
> >   0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> >   1 packages not fully installed or removed.
> >   Need to get 0B of archives. After unpacking 0B will be used.
> >   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)
> >
> > Does anybodu have any idea of how to fix this?
> >
> > Thanks,
> > Erik

-- 
+----------------------------------------------------------+
  Erik de Castro Lopo  nospam@mega-nerd.com (Yes its valid)
+----------------------------------------------------------+
Those who do not understand Unix are condemned to reinvent it, poorly.  
-- Henry Spencer



Reply to: