From: "Michael Veksler" <VEKSLER@il.ibm.com>
To: gardiol@libero.it
Cc: gcc-help@gcc.gnu.org
Subject: Re: using gcc 3.0.1 and 2.95.2.1
Date: Tue, 11 Sep 2001 01:04:00 -0000 [thread overview]
Message-ID: <OFB1BF9E68.34D77FF4-ONC2256AC4.002A0893@telaviv.ibm.com> (raw)
> I am trying to compile kdevelop 2.0 but i get an error
> compiling flex related stuff (flex 2.5.4a)
Flex (the one that I have) creates non standard c++ code.
The ungly hack that I have runs sed on the result of flex,
and replaces 'class istream;' with '#include <iosfwd.h>".
"iosfwd.h" is a file I wrote that includes iosfwd, and has
several "using std::one-of-iostream-classes;" lines.
> So i decided to install a second gcc: 2.905.2.1
You mean gcc-2.95.2, right ?
> (/usr/local/gcc-2.95.2) and use it to compile KDevelop.
> It works, BUT if i try to compile with that gcc i get
> tons (really tons) of udefined symbol!
> Now i suspect gcc from 2.x to 3.x uses a different naming
> for c++ symbols but how can i overcome this problem?
Maybe recompile every single C++ library you have with the same C++
compiler?
The ABI of gcc C++ has changed every release (except for patch level
releases). This means that C++ code you compiled (or somebody else
compiled for you), cannot be mixed with C++ code compiled with different
gcc versions.
It *may* be possible to mix two different C++ versions in a single program
by using C or CORBA proxies, but I guess you are not that desperate.
Michael
next reply other threads:[~2001-09-11 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-11 1:04 Michael Veksler [this message]
2001-09-11 3:46 ` Willy Gardiol
-- strict thread matches above, loose matches on Subject: below --
2001-09-11 5:44 Michael Veksler
2001-09-11 0:22 Willy Gardiol
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=OFB1BF9E68.34D77FF4-ONC2256AC4.002A0893@telaviv.ibm.com \
--to=veksler@il.ibm.com \
--cc=gardiol@libero.it \
--cc=gcc-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).