From: Alex Buell <alex.buell@tahallah.demon.co.uk>
To: Doug Landauer <landauer@apple.com>
Cc: gcc@gcc.gnu.org
Subject: Re: ABI/compatibility details? (egcs -> gcc 2.95 -> future?)
Date: Thu, 30 Sep 1999 18:02:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.10.9909202212380.852-100000@tahallah.demon.co.uk> (raw)
Message-ID: <19990930180200.sWJ8F4ERf53uc7L0d87cEoWsVg8jEYNkDPGFOnSbnhg@z> (raw)
In-Reply-To: <v03102807b40c51eeb5e6@[17.202.40.190]>
On Mon, 20 Sep 1999, Doug Landauer wrote:
> Is there a more detailed description of what the known
> incompatibilities are, and/or what C++ features might trigger them,
> and/or whether there is a subset of C++ that one might reasonably
> expect to work compatibly, say from egcs 1.1 to gcc 2.95?
I ran into this problem with my Linux system. As most of the libraries had
been compiled with egcs-1.0.3, egcs-1.1.1, egcs-1.1.2, and when I moved to
gcc-2.95.1, everything went to hell. :o(
Solution was to recompile nearly everything. Fortunately, I've got ~600MB
sources on a CD so it was just a matter of rebuilding all the critical
libraries, and then fixing the rest as I find them.
Cheers,
Alex
--
Legalise cannabis today!
http://www.tahallah.demon.co.uk - updated!
next prev parent reply other threads:[~1999-09-30 18:02 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-20 11:20 egcs and altivec vector type David Young
1999-09-20 14:10 ` ABI/compatibility details? (egcs -> gcc 2.95 -> future?) Doug Landauer
1999-09-20 14:17 ` Alex Buell [this message]
1999-09-20 15:04 ` Martin v. Loewis
1999-09-20 15:16 ` Alex Buell
1999-09-20 15:46 ` Martin v. Loewis
1999-09-20 17:34 ` Alexandre Oliva
1999-09-21 0:00 ` Alex Buell
1999-09-30 18:02 ` Alex Buell
1999-09-30 18:02 ` Alexandre Oliva
1999-09-21 1:26 ` Wolfram Gloger
1999-09-21 12:16 ` Alex Buell
1999-09-22 1:09 ` Wolfram Gloger
1999-09-22 15:29 ` Alex Buell
1999-09-30 18:02 ` Alex Buell
1999-09-30 18:02 ` Wolfram Gloger
1999-09-30 18:02 ` Alex Buell
1999-09-30 18:02 ` Wolfram Gloger
1999-09-30 18:02 ` Martin v. Loewis
1999-09-30 18:02 ` Alex Buell
1999-09-30 18:02 ` Martin v. Loewis
1999-09-30 18:02 ` Alex Buell
1999-09-20 15:23 ` Martin v. Loewis
1999-09-24 13:10 ` Gerald Pfeifer
1999-09-30 18:02 ` Gerald Pfeifer
1999-10-08 10:36 ` Martin v. Loewis
1999-10-31 23:35 ` Martin v. Loewis
1999-09-30 18:02 ` Martin v. Loewis
1999-09-30 18:02 ` Doug Landauer
1999-09-21 10:10 ` egcs and altivec vector type David Edelsohn
1999-09-22 7:09 ` David Young
1999-09-22 7:14 ` Gerald Pfeifer
1999-09-30 18:02 ` Gerald Pfeifer
1999-09-30 18:02 ` David Young
1999-09-30 18:02 ` David Edelsohn
1999-09-30 18:02 ` David Young
1999-10-08 11:38 ABI/compatibility details? (egcs -> gcc 2.95 -> future?) Mike Stump
1999-10-08 11:48 ` Gerald Pfeifer
1999-10-08 13:28 ` Mark Mitchell
1999-10-08 22:05 ` Gerald Pfeifer
1999-10-09 4:10 ` Martin v. Loewis
1999-10-31 23:35 ` Martin v. Loewis
1999-10-31 23:35 ` Gerald Pfeifer
1999-10-31 23:35 ` Mark Mitchell
1999-10-31 23:35 ` Gerald Pfeifer
1999-10-31 23:35 ` Mike Stump
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=Pine.LNX.4.10.9909202212380.852-100000@tahallah.demon.co.uk \
--to=alex.buell@tahallah.demon.co.uk \
--cc=gcc@gcc.gnu.org \
--cc=landauer@apple.com \
/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).