From: Ian Lance Taylor <iant@google.com>
To: "Weaver\, John P CIV" <john.p.weaver@navy.mil>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: prefer static linking
Date: Tue, 29 Nov 2011 23:56:00 -0000 [thread overview]
Message-ID: <mcrk46iwxa4.fsf@dhcp-172-18-216-180.mtv.corp.google.com> (raw)
In-Reply-To: <869832256C376241BB63955DA5CA5AA702B53725@nawechlkez01v.nadsuswe.nads.navy.mil> (John P. Weaver's message of "Tue, 29 Nov 2011 11:02:24 -0800")
"Weaver, John P CIV" <john.p.weaver@navy.mil> writes:
> The gcc compiler prefers to use dynamic libraries in the linking
> phase. When porting software from one machine to another it is
> frequently desirable to link to static libraries as much as possible
> to account for different versions of the libraries. The -static flag
> is useful when you do not need any dynamic library support but causes
> the linker to fail if there is only a dynamic library for a particular
> call. Is there a way to ask the linker to use static libraries when
> possible and report the dynamic libraries that are needed to complete
> the linking process?
I am not aware of any such option.
If you are using the GNU linker, you can tell it to prefer dynamic
libraries using -Bdynamic and tell it to use only static libraries using
-Bstatic, but I don't know of any option to tell it to prefer static
libraries but use dynamic libraries if they are available.
Ian
next prev parent reply other threads:[~2011-11-29 19:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 23:47 Weaver, John P CIV
2011-11-29 23:56 ` Ian Lance Taylor [this message]
2011-11-30 1:29 ` Weaver, John P CIV
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=mcrk46iwxa4.fsf@dhcp-172-18-216-180.mtv.corp.google.com \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=john.p.weaver@navy.mil \
/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).