From: Ian Pilcher <arequipeno@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Environment variable equivalent of -L
Date: Mon, 28 Mar 2022 09:43:45 -0500 [thread overview]
Message-ID: <601f3d61-b21b-5fe2-45f6-dd0e8bcc28fe@gmail.com> (raw)
In-Reply-To: <20220328143554.GJ614@gate.crashing.org>
On 3/28/22 09:35, Segher Boessenkool wrote:
> You could use what in DOS was called a response file:
> '@FILE'
> Read command-line options from FILE. The options read are inserted
> in place of the original @FILE option. If FILE does not exist, or
> cannot be read, then the option will be treated literally, and not
> removed.
I could also add the paths that I need to a variable of my own invention
and pass that on the command line, e.g.:
$ mips-openwrt-linux-musl-gcc ... -L${MY_LIB_PATHS} ...
I just seems a bit weird that GCC honors CPATH and friends for header
file locations, but there doesn't seem to be any equivalent for library
paths.
--
========================================================================
Google Where SkyNet meets Idiocracy
========================================================================
prev parent reply other threads:[~2022-03-28 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 14:04 Ian Pilcher
2022-03-28 14:35 ` Segher Boessenkool
2022-03-28 14:43 ` Ian Pilcher [this message]
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=601f3d61-b21b-5fe2-45f6-dd0e8bcc28fe@gmail.com \
--to=arequipeno@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=segher@kernel.crashing.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).