From: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
To: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
Cc: gregzh@yahoo.com, gcc-help@gcc.gnu.org
Subject: Re: More than one lib file
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <org0tzfbrf.fsf@garnize.lsd.ic.unicamp.br> (raw)
Message-ID: <20000401000000.kgxr0P_GV6WvKW_f1tvPDboBjjSu6pXdrJl2pevnXu0@z> (raw)
In-Reply-To: <200003100832.JAA01061@loewis.home.cs.tu-berlin.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]
On Mar 10, 2000, "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de> wrote:
>> So, could give me a advice how and where to begin
>> this?
> Are they using two different gcc installations as well? If so, you can
> put libstdc++ into the directory where cc1plus lives; gcc will pick it
> up from there. After you've made the change, you should verify with
> gcc -v that it does the right thing.
It's not just a matter of GCC finding the right library: if it's a
dynamic library, the executable will have to find it too, and that's
where the problems may start. If the library sonames are different,
there should be no problem if both are in /usr/local/lib. But if
they're not, you may have to add -R/path/to/the/right/library to the
link command in order for the executable to find the appropriate
library at run-time.
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva/ Enjoy Guaraná
Cygnus Solutions, a Red Hat company aoliva@{redhat, cygnus}.com
Free Software Developer and Evangelist CS PhD student at IC-Unicamp
oliva@{lsd.ic.unicamp.br, gnu.org} Write to mailing lists, not to me
next prev parent reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-09 13:45 greg zhang
2000-03-10 0:38 ` Martin v. Loewis
2000-03-10 0:52 ` Alexandre Oliva [this message]
2000-04-01 0:00 ` Alexandre Oliva
2000-04-01 0:00 ` Martin v. Loewis
2000-04-01 0:00 ` greg zhang
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=org0tzfbrf.fsf@garnize.lsd.ic.unicamp.br \
--to=oliva@lsd.ic.unicamp.br \
--cc=gcc-help@gcc.gnu.org \
--cc=gregzh@yahoo.com \
--cc=martin@loewis.home.cs.tu-berlin.de \
/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).