From: _hate_spam_thunder7@xs4all.nl (jwk)
To: help-gcc@gnu.org
Subject: sig11 when compiling gcc (2.95/2.95.1/egcs-1.1.2) - software problem
Date: Sun, 05 Sep 1999 22:36:00 -0000 [thread overview]
Message-ID: <slrn7t6jvk.qu5._hate_spam_thunder7@middle.of.nowhere> (raw)
All gcc versions I tried die when using xgcc for the first time. Now I
know this is a software problem, since on a clean RH 5.2 install on
another partition I can compile 20 times without error, and if I chroot
to that partition, things also work well.
Now to the solution: does anybody have any hints what to check first? I
cleaned out all remnants of gcc-installations from /usr/local/bin, what
should be next? Checking /usr/bin, or checking libraries - if so, which
ones?
I hope someone more knowledgable than me has any ideas here - the
prospect of re-installation is a bit daunting....
Jurriaan
WARNING: multiple messages have this Message-ID
From: _hate_spam_thunder7@xs4all.nl (jwk)
To: help-gcc@gnu.org
Subject: sig11 when compiling gcc (2.95/2.95.1/egcs-1.1.2) - software problem
Date: Thu, 30 Sep 1999 23:56:00 -0000 [thread overview]
Message-ID: <slrn7t6jvk.qu5._hate_spam_thunder7@middle.of.nowhere> (raw)
Message-ID: <19990930235600.GmDqytRJzeNROC6qgrhyG2dTdHxa4Vric_j4AjugkOo@z> (raw)
All gcc versions I tried die when using xgcc for the first time. Now I
know this is a software problem, since on a clean RH 5.2 install on
another partition I can compile 20 times without error, and if I chroot
to that partition, things also work well.
Now to the solution: does anybody have any hints what to check first? I
cleaned out all remnants of gcc-installations from /usr/local/bin, what
should be next? Checking /usr/bin, or checking libraries - if so, which
ones?
I hope someone more knowledgable than me has any ideas here - the
prospect of re-installation is a bit daunting....
Jurriaan
WARNING: multiple messages have this Message-ID
From: _hate_spam_thunder7@xs4all.nl (jwk)
To: help-gcc@gnu.org
Subject: sig11 when compiling gcc (2.95/2.95.1/egcs-1.1.2) - software problem
Date: Fri, 01 Oct 1999 00:00:00 -0000 [thread overview]
Message-ID: <slrn7t6jvk.qu5._hate_spam_thunder7@middle.of.nowhere> (raw)
Message-ID: <19991001000000.oXvNVvBgfwhrTOofO2oOLkpwdWOZDTppiaggobzBXV4@z> (raw)
All gcc versions I tried die when using xgcc for the first time. Now I
know this is a software problem, since on a clean RH 5.2 install on
another partition I can compile 20 times without error, and if I chroot
to that partition, things also work well.
Now to the solution: does anybody have any hints what to check first? I
cleaned out all remnants of gcc-installations from /usr/local/bin, what
should be next? Checking /usr/bin, or checking libraries - if so, which
ones?
I hope someone more knowledgable than me has any ideas here - the
prospect of re-installation is a bit daunting....
Jurriaan
next reply other threads:[~1999-09-05 22:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-05 22:36 jwk [this message]
1999-09-06 6:04 ` Graham Seaman
1999-09-06 11:38 ` jwk
1999-09-30 23:56 ` jwk
1999-10-01 0:00 ` jwk
1999-09-06 14:45 ` jwk
1999-09-30 23:56 ` jwk
1999-10-01 0:00 ` jwk
1999-09-07 3:26 ` Renaud Pons
1999-09-30 23:56 ` Renaud Pons
1999-10-01 0:00 ` Renaud Pons
1999-09-30 23:56 ` Graham Seaman
1999-10-01 0:00 ` Graham Seaman
1999-09-30 23:56 ` jwk
1999-10-01 0:00 ` jwk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=slrn7t6jvk.qu5._hate_spam_thunder7@middle.of.nowhere \
--to=_hate_spam_thunder7@xs4all.nl \
--cc=help-gcc@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).