From: Alexandre Oliva <aoliva@redhat.com>
To: Geoff Keating <geoffk@geoffk.org>
Cc: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>, gcc-patches@gcc.gnu.org
Subject: Re: rewrite lib/g77.exp
Date: Tue, 13 Nov 2001 15:03:00 -0000 [thread overview]
Message-ID: <orwv0qhtcx.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: Geoff Keating's message of "29 Oct 2001 12:52:54 -0800"
On Oct 29, 2001, Geoff Keating <geoffk@geoffk.org> wrote:
> "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu> writes:
>> > From: Geoff Keating <geoffk@geoffk.org>
>> > I'm sure the problem is with the second of these lines:
>> >
>> > if [file exists "${gccpath}/libf2c/.libs/libg2c.so"] {
>> > append flags "-Wl,--rpath-link,${rootme} "
>> > append ld_library_path ":${gccpath}/libf2c/.libs"
>> > }
>> >
>> > which is GNU ld specific; it aims to ensure that the just-built
>> > libgcc_s.so is linked against. Can you propose a substitute for it
>> > that works with both Solaris ld and GNU ld?
>>
>>
>> What's wrong with:
>>
>> > append ld_library_path ":${rootme}"
>>
>> like in g++.exp?
> It's not enough. (You can see that g77.exp does in fact have that line.)
> It's possible this is a linker bug.
I recall a number of dynamic loaders will disregard LD_LIBRARY_PATH
when looking for dependencies of shared libraries. This is one of the
reasons why I recommend using libtool for libgcc: then libtool will
know how to arrange for libg2c.la to find libgcc_s.so in the build
tree, and then, after they're installed, the installed copy of
libg2c.so will find libgcc_s.so in the install tree.
#include usual caveats about encoding search paths into shared
libraries, and why they're good for many and bad for many others
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next prev parent reply other threads:[~2001-11-17 5:14 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-28 16:51 Kaveh R. Ghazi
[not found] ` <jm3d42qic9.fsf@geoffk.org>
2001-11-13 15:03 ` Alexandre Oliva [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-13 15:03 Kaveh R. Ghazi
2001-11-14 15:45 ` Alexandre Oliva
2001-11-14 16:42 ` Geoff Keating
2001-11-14 17:05 ` Alexandre Oliva
2001-11-14 17:18 ` Geoff Keating
2001-11-14 17:24 ` Alexandre Oliva
2001-11-15 18:36 ` Geoff Keating
2001-11-16 12:45 ` Alexandre Oliva
2001-11-26 22:44 ` Alexandre Oliva
2001-11-26 13:09 ` Geoff Keating
2001-11-24 23:46 ` Alexandre Oliva
2001-11-24 23:27 ` Geoff Keating
2001-11-24 22:38 ` Alexandre Oliva
2001-11-24 22:15 ` Geoff Keating
2001-11-14 16:55 ` Zack Weinberg
2001-11-14 17:05 ` Alexandre Oliva
2001-11-14 17:14 ` Zack Weinberg
2001-11-14 17:20 ` Alexandre Oliva
2001-11-24 23:44 ` Alexandre Oliva
2001-11-24 22:49 ` Zack Weinberg
2001-11-24 22:28 ` Alexandre Oliva
2001-11-24 22:23 ` Zack Weinberg
2001-11-24 19:55 ` Alexandre Oliva
2001-10-28 5:44 Kaveh R. Ghazi
2001-10-28 9:37 ` Geoff Keating
2001-10-28 9:56 ` Franz Sirl
[not found] ` <REFOR1kDTM9wGmAf0Mj00001d53@eforward1.enom.com>
2001-10-28 10:10 ` Geoff Keating
2001-10-28 10:19 ` Franz Sirl
2001-10-23 13:42 Geoffrey Keating
2001-10-23 13:57 ` Joseph S. Myers
2001-10-23 14:40 ` Geoff Keating
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=orwv0qhtcx.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=geoffk@geoffk.org \
--cc=ghazi@caip.rutgers.edu \
/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).