public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: jvl072170@cse.iitd.ernet.in
To: gcc-help@gcc.gnu.org
Subject: Re: Binary compatibility of gcc 3.4.4 and gcc 4.2.0
Date: Tue, 17 Mar 2009 04:34:00 -0000	[thread overview]
Message-ID: <41092.57.73.25.165.1237264479.squirrel@www.cse.iitd.ernet.in> (raw)
In-Reply-To: <alpine.DEB.2.00.0903162332320.669@stedding.loria.fr>

Yes,

Since libstdc++.so.6.0.8 is a higher version over libstdc++.so.6.0.3,
are they not binary compatible??
Do they use the same or different name mangling algorithms??

When the application binary interface of GNU gcc 3.4.4 and GNU gcc 4.2.0
is same, what else do we need to see to check their compatibility?

My work environment is g++ 4.2.0 but my program has to link with a static
library which has been compiled with g++ 3.4.4.













On Mon, 16 Mar 2009, Andrew Haley wrote:
>
>>> I want to build a program in GNU g++ 4.2.0 linking it with a static
>>> librrayd object built using gcc 3.4.4. Does the libxyz.a compiled using
>>> gcc 3.4.4 link properly with a program being compiled using gcc 4.2.0
>>
>> Usually yes, but not with C++.
>>
>>> I checked both the compilers use ABI version 2.
>>> Version 4.2.o uses libstdc++.so.6.0.8 while 3.4.4. uses
>>> libstdc++.so.6.0.3.
>>> What is the diffrence among these two versions of libstdc++??
>>
>> These libraries are not binary compatible, sorry.  You'll have to
>> recompile.
>
> Are you sure about that? They are both libstdc++.so.6, so the more recent
> version is supposed to be backwards compatible with the older one. Or were
> you talking about something else?
>
> To the OP: not saying what error you get does not help...
>
> --
> Marc Glisse
>


      reply	other threads:[~2009-03-17  4:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16  9:23 jvl072170
2009-03-16 10:01 ` Andrew Haley
2009-03-16 22:41   ` Marc Glisse
2009-03-17  4:34     ` jvl072170 [this message]

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=41092.57.73.25.165.1237264479.squirrel@www.cse.iitd.ernet.in \
    --to=jvl072170@cse.iitd.ernet.in \
    --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).