From: David Wragg <dpw@doc.ic.ac.uk>
To: help-gcc@gnu.org
Subject: Re: what is -rpath supposed to do?
Date: Thu, 09 Dec 1999 16:32:00 -0000 [thread overview]
Message-ID: <jak8mnoczr.fsf@gatsby.u-net.com> (raw)
In-Reply-To: <slrn84vaet.eu.nubis@ban.osiris.home>
nubis@ban.osiris.home () writes:
> On Thu, 9 Dec 1999 10:59:17 +0100, Cegetel <Cegetel@Cegetel.com>
> wrote:
> >Hi all, I'm trying to build Apache 1.3.9 for my Linux box (Suse 6.2).
> >But there's a -rpath option used in the configuration file that seems
> >not to be known by gcc... As you could expect, a path follows this
> >option...
>
> The -rpath option should given to the linker ld. It is the same as -L
> for gcc. I rember compiling apache I had the same problem and changed
> all -rpath to -L in the Makefiles. Maybe not the propper method to
> this, but worked for me.
-rpath is certainly not the same as -L. They have very different
purposes; see the ld info pages for what -rpath really does.
gcc does not understand -rpath, because it is a linker option. It
seems strange that apache would be passing this to gcc. The fix is to
tell gcc that the -rpath option should be passed on to the linker,
with -Wl,-rpath,<arg>
David Wragg
WARNING: multiple messages have this Message-ID
From: David Wragg <dpw@doc.ic.ac.uk>
To: help-gcc@gnu.org
Subject: Re: what is -rpath supposed to do?
Date: Fri, 31 Dec 1999 22:24:00 -0000 [thread overview]
Message-ID: <jak8mnoczr.fsf@gatsby.u-net.com> (raw)
Message-ID: <19991231222400.kjr_eFTYmc8yV6wnqhs4Gb2OeigbpaGdhiI8_thPxo8@z> (raw)
In-Reply-To: <slrn84vaet.eu.nubis@ban.osiris.home>
nubis@ban.osiris.home () writes:
> On Thu, 9 Dec 1999 10:59:17 +0100, Cegetel <Cegetel@Cegetel.com>
> wrote:
> >Hi all, I'm trying to build Apache 1.3.9 for my Linux box (Suse 6.2).
> >But there's a -rpath option used in the configuration file that seems
> >not to be known by gcc... As you could expect, a path follows this
> >option...
>
> The -rpath option should given to the linker ld. It is the same as -L
> for gcc. I rember compiling apache I had the same problem and changed
> all -rpath to -L in the Makefiles. Maybe not the propper method to
> this, but worked for me.
-rpath is certainly not the same as -L. They have very different
purposes; see the ld info pages for what -rpath really does.
gcc does not understand -rpath, because it is a linker option. It
seems strange that apache would be passing this to gcc. The fix is to
tell gcc that the -rpath option should be passed on to the linker,
with -Wl,-rpath,<arg>
David Wragg
next prev parent reply other threads:[~1999-12-09 16:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-09 2:33 Cegetel
1999-12-09 4:30 ` nubis
1999-12-09 16:32 ` David Wragg [this message]
1999-12-10 0:27 ` Stuart Summerville
1999-12-31 22:24 ` Stuart Summerville
1999-12-31 22:24 ` David Wragg
1999-12-31 22:24 ` nubis
1999-12-31 22:24 ` Cegetel
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=jak8mnoczr.fsf@gatsby.u-net.com \
--to=dpw@doc.ic.ac.uk \
--cc=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).