From: Segher Boessenkool <segher@kernel.crashing.org>
To: Ian Pilcher <arequipeno@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Environment variable equivalent of -L
Date: Mon, 28 Mar 2022 09:35:54 -0500 [thread overview]
Message-ID: <20220328143554.GJ614@gate.crashing.org> (raw)
In-Reply-To: <t1sfa6$4ue$1@ciao.gmane.io>
On Mon, Mar 28, 2022 at 09:04:53AM -0500, Ian Pilcher via Gcc-help wrote:
> I am using GCC as a cross compiler, which results in some crazy long
> command lines, because of all the directories that need to be passed
> with the -I and -L options.
>
> I've found the CPATH variable, for include file paths (-I equivalent),
> but I haven't found anything that works like -L. I tried LIBRARY_PATH,
> but that didn't work.
>
> Am I missing something, or is there just no such variable?
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.
Segher
next prev parent reply other threads:[~2022-03-28 14:36 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 [this message]
2022-03-28 14:43 ` Ian Pilcher
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=20220328143554.GJ614@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=arequipeno@gmail.com \
--cc=gcc-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).