Skip to Content.
Sympa Menu

sm-users - Re: [smgl] Re: [SM-Users] GCC disappeared

sm-users AT lists.ibiblio.org

Subject: Sourcemage Users List

List archive

Chronological Thread  
  • From: Treeve Jelbert <treeve01 AT pi.be>
  • To: sm-users AT lists.ibiblio.org
  • Subject: Re: [smgl] Re: [SM-Users] GCC disappeared
  • Date: Wed, 19 Nov 2003 20:35:57 +0100

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 19 November 2003 18:42, Eric Sandall wrote:
> Quoting Peter Schneider-Kamp <psk AT informatik.rwth-aachen.de>:
>
> > Hi!
> >
> > I've got a problem with my SourceMage installation on my notebook.
> >
> > When I tried to upgrade from gcc 2.95.3 to 3.3.2 there
> > was a problem with some header file /usr/include/signal.h
> >
> > Using gaze from I located this file to be part of glibc.
> > Having installed glibc 2.2.5 I reckoned an upgrade to
> > 2.3.2 might make the compile of gcc go through.
> >
> > Unfortunately, it seems that the old gcc has been dispelled.
> > There is this signal.h error in the compile log, but it
> > looks like the compile and install went through anyway.
> >
> > Now, I have g++ in /usr/bin but no gcc. And no
> > libgcc_s.so ... and so on.
> >
> > Two questions:
> >
> > a) Why did the compile go through although there was an error?
> >
> > and more importantly
> >
> > b) How can get a working gcc again? Unfortunately, because
> > hard disk space is rare on this notebook, I do not keep
> > a cached version in /var/cache/sorcery.
> >
> > Any help is appreciated,
> > Peter
>
>
> Hmm...looks like you haven't been keeping up-to-date with fixes. ;)
>
> I'm not sure why gcc went all the way through, there may be some missing
> ampersands in the BUILD file (or another file), or their Makefile isn't
> properly setup to fail on a failure.
>
> As for getting a working gcc, if you have another machine, you can have it
> compile a new gcc (you can even use the CROSS_COMPILE feature in
> Sorcery->Option->Feature Menu ;)) to compile a copy of gcc for your
> laptop's
architecture, then untar the archived copy of that onto "/" of
> your laptop. That should get gcc working again (you can do this for any
> package, generally).
>



what about extracting a gcc from an iso
>
Regards, Treeve

- --
PGP Key ID: AB929B24
PGP Key Fingerprint:31D9 D22F 42E6 F545 662E AB6F 9697 34C5 AB92 9B24
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/u8Yllpc0xauSmyQRArCTAKCtqa/wMMtEvy1hydDccAr9TMf1SgCfeDRb
8lEp5197t/YSxaY+3/nljX8=
=2DsP
-----END PGP SIGNATURE-----




Archive powered by MHonArc 2.6.24.

Top of Page