public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Amos A Gouaux <amos@utdallas.edu>
To: Alexandre Oliva <oliva@dcc.unicamp.br>
Cc: egcs@cygnus.com
Subject: Re: Including -R /usr/local/lib?
Date: Sun, 19 Apr 1998 18:48:00 -0000	[thread overview]
Message-ID: <Pine.GSO.3.96.980419173653.24122B-100000@velcro.utdallas.edu> (raw)
In-Reply-To: <orlnt2d435.fsf@cuca.lsd.dcc.unicamp.br>

First, I apologize for not searching the web list archives more
extensively.  I searched the last two months and didn't see any
solutions, then I posted.  If I searched the very next month I
would have come across the more lengthy thread. 

BTW, can a search page be added?  On SunSolve, you can specify
which "collections" to search, how many months back to search,
and how many responses to return.  Here, the collections could be
the various egcs lists.  Considering the size of this project,
some kind of more intelligent searching mechanism would really be
helpful.

On 18 Apr 1998, Alexandre Oliva wrote:

> 1) modify the specs file (/usr/local/lib/gcc-lib/*/*/specs) and add -R
> to the `*link:' or `*lib:' pattern

I'm not familiar with the syntax of this file, so instead tried
the following suggestion. 

> 2) modify `libstdc++/config/*.ml' and modify the `-h' or `-soname'
> switch so that it includes the full pathname of the library.

Indeed, this works just fine.  Actually, this might even be
better since one could still use LD_RUN_PATH, if absolutely
necessary.  The specs file approach would render LD_RUN_PATH
useless. 

Since it was raised, I would agree that g++ should not
arbitrarily add -R all over the place.  However, since g++
automatically links in libstdc++, it seems reasonable that the
resulting executable should at least be able to find this
library.  Altering sol2shm.ml took care of this nicely. 

Thanks.

amos



  parent reply	other threads:[~1998-04-19 18:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-18  8:31 Amos A Gouaux
1998-04-18 16:05 ` Martin von Loewis
1998-04-18 18:00 ` Alexandre Oliva
1998-04-19  8:38   ` Kamil Iskra
1998-04-19  8:15     ` Alexandre Oliva
1998-04-19 18:48   ` Amos A Gouaux [this message]
1998-04-19 18:10 ` Joe Buck

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=Pine.GSO.3.96.980419173653.24122B-100000@velcro.utdallas.edu \
    --to=amos@utdallas.edu \
    --cc=egcs@cygnus.com \
    --cc=oliva@dcc.unicamp.br \
    /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).