From: Oscar Fuentes <ofv@wanadoo.es>
To: gcc-help@gcc.gnu.org
Subject: Re: Link problems
Date: Thu, 08 Aug 2002 09:08:00 -0000 [thread overview]
Message-ID: <sn1p72qw.fsf@wanadoo.es> (raw)
In-Reply-To: <3D5275F7.43A7E06A@fastmail.fm>
bjorn rohde jensen <bjensen@fastmail.fm> writes:
> Hi Jarmo,
>
> You can not in general crosslink object code generated by
> different compilers. You should use one and only one
> compiler to create an application. One does usually not
> have to rebuild the system C libraries, but C++ libs etc
> definitely should be.
> The unresolved symbols are probably due to different
> name mangling schemes employed by gcc-2.96, which is not
> actually an official gcc release, and gcc-3.0.4. This is
> done to protect users from linking incompatible object
> files to create applications with spectacularly odd behaviour,
> such as random core dumps despite code correctness and so on.
Actually, that incompatibility among gcc 2.9x and gcc 3.x comes from
the introduction of a new "standard" C++ ABI on the gcc 3.x
series. One of the main goals of the new ABI is to allow the
interchange of object code among different C++ compilers which use
said ABI.
--
Oscar
next prev parent reply other threads:[~2002-08-08 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 6:20 Jarmo
2002-08-08 6:45 ` bjorn rohde jensen
2002-08-08 9:08 ` Oscar Fuentes [this message]
2002-08-08 9:39 ` bjorn rohde jensen
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=sn1p72qw.fsf@wanadoo.es \
--to=ofv@wanadoo.es \
--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).