public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
To: PATRICK.O.CESARD@saic.com
Cc: help-gcc@gnu.org
Subject: Re: About GCC and the -R option (a linker option I believe)
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <200003301740.TAA00797@loewis.home.cs.tu-berlin.de> (raw)
Message-ID: <20000401000000.LxPqGz7W-CebHyFccdYntLPBLNQn0cPiY8IEQ2k1F9c@z> (raw)
In-Reply-To: <3C8C1135B453D311870C0008C7916A040C93D5@mcl-its-exs03.mail.saic.com>

> I have been reading the gcc manual entitled "Using and Porting the GNU
> Compiler Collection" but cannot find any documentation about the -R option
> used to include shared library directory paths in an executable.  I've
> used this option with gcc on my Solaris 2.7 machine and it works but it is
> not recognized by gcc on my HPUX10-20 machine. That's why I decided to
> actually look it up the gcc manual.

This option is not a gcc option, but a linker option. GCC recognizes
some of the assembler and linker options of the native tools, and
passes them through to those tools. What those options are highly
depends on the platform, and possibly on the exact version of the
assembler and linker.

It is safer to use use the -Wl, option of gcc to pass options to the
linker, that way, there is no confusion with options to other
passes. You'll have to look for the equivalent of -R in your linker
documentation, then.

Regards,
Martin

  reply	other threads:[~2000-04-01  0:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-30  7:38 Cesard, Patrick O.
2000-03-30  9:45 ` Martin v. Loewis [this message]
2000-04-01  0:00   ` Martin v. Loewis
2000-04-01  0:00 ` Cesard, Patrick O.

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=200003301740.TAA00797@loewis.home.cs.tu-berlin.de \
    --to=martin@loewis.home.cs.tu-berlin.de \
    --cc=PATRICK.O.CESARD@saic.com \
    --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).