From: "Miguel Angel Núñez" <miguel.nunez@datatronics.es>
To: gcc-help@gcc.gnu.org, Oscar Fuentes <ofv@wanadoo.es>
Subject: Re[2]: 2.95.2 libraries donŽt link using 3.x
Date: Fri, 19 Jul 2002 00:08:00 -0000 [thread overview]
Message-ID: <14459297193.20020719091348@datatronics.es> (raw)
In-Reply-To: <bs95vtjy.fsf@wanadoo.es>
Hola Oscar,
Yes, I was talking about C++. Upps, I forgot to mention it.
My problem is that the 2.95.2 libraries are comercial ones, so I don't
have the source code. I only have the binaries. The vovida source code
does not compile using gcc lower than 3.x.
I'm afraid I will have to produce 2 executables and communicate them
in any way.
There is not really any way to link 2.x and 3.x binaries together in
the same executable? This is my last chance, and I will not ask any
more ;-)
Thanks a lot Oscar!!
Thursday, July 18, 2002, 7:23:45 PM, usted escribió:
OF> Miguel Angel Núñez <miguel.nunez@datatronics.es> writes:
>> Hello GCC experts,
>>
>> I hope you can help me in this link problem that I donÂŽt know how to
>> solve.
>>
>> I'm using some libraries that were developed for GCC 2.95.2. I was
>> using GCC 2.95.3 and everything was fine. My application was compiled
>> and linked perfectly.
>>
>> Now I have to use GCC 3.x because of some source code I'm including
>> from www.vovida.org that needs this version of GCC. The application
>> is compiled, but at link time I get a lot of errors about undefined
>> symbols (all of them in the libraries for 2.95.2).
>>
>> My question:
>> Is there any modifier for having backwards compatibility? Compile
>> 3.x code, and link against 3.x libraries and 2.95.2 libraries.
>>
>> Is this possible?
OF> I guess you are talking about C++ (remember: GCC is 5 languages or so)
OF> The C++ ABI changed on gcc 3.0.x The new ABI and the previous one are
OF> incompatible.
>>
>> Any other idea about how to overcome this problem is very welcome.
OF> You must re-build all your libraries with gcc 3.x if you want to use
OF> it. Those binaries will not be compatible with gcc < 3.0
prev parent reply other threads:[~2002-07-19 7:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 10:12 Miguel Angel Núñez
2002-07-18 10:23 ` Oscar Fuentes
2002-07-19 0:08 ` Miguel Angel Núñez [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=14459297193.20020719091348@datatronics.es \
--to=miguel.nunez@datatronics.es \
--cc=gcc-help@gcc.gnu.org \
--cc=ofv@wanadoo.es \
/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).