From: Ian Lance Taylor <iant@google.com>
To: "Rohit Arul Raj" <rohitarulraj@gmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Invoking static library automatically
Date: Fri, 01 Dec 2006 15:22:00 -0000 [thread overview]
Message-ID: <m3fybzfxqd.fsf@localhost.localdomain> (raw)
In-Reply-To: <c356fd4e0611302345r237dfba0g4837efd729e40df8@mail.gmail.com>
"Rohit Arul Raj" <rohitarulraj@gmail.com> writes:
> I have built a static runtime library and i want the linker to access
> it automatically without having to pass it explicitly.
>
> Are there any environmental variables available to make this happen?
I'm not aware of any environment variable which directs the linker to
automatically include a library. If there were one, it would be
documented in the linker manual:
http://sourceware.org/binutils/docs-2.17/ld/index.html
You can force the linker to always include a library by changing the
linker script, but of course then you have to tell the linker to use
your new linker script.
Ian
prev parent reply other threads:[~2006-12-01 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 7:45 Rohit Arul Raj
2006-12-01 15:22 ` Ian Lance Taylor [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=m3fybzfxqd.fsf@localhost.localdomain \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=rohitarulraj@gmail.com \
/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).