From: "Alfred M. Szmidt" <ams@gnu.org>
To: Andrew Haley <aph@redhat.com>
Cc: divisortheory@gmail.com, gcc@gcc.gnu.org
Subject: Re: Problem with static linking
Date: Thu, 16 Jul 2009 13:54:00 -0000 [thread overview]
Message-ID: <E1MRRPM-00069A-P4@fencepost.gnu.org> (raw)
In-Reply-To: <4A5ED994.2010301@redhat.com> (message from Andrew Haley on Thu, 16 Jul 2009 08:41:08 +0100)
However, I really implore you: by all means link statically to
everything else, but leave libc dynamically linked. I'm not aware
of any reason not to link libc dynamically, and not doing so leads
to a ton of problems.
Problems also arise if one uses functions that use NSS (eg. getXbyY
functions like gethostbyname). In which case, the GNU C library will
try to do a dlopen on several libraries to find the right one.
next prev parent reply other threads:[~2009-07-16 13:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 2:37 Zachary Turner
2009-07-16 3:42 ` Ian Lance Taylor
2009-07-16 7:41 ` Andrew Haley
2009-07-16 13:54 ` Alfred M. Szmidt [this message]
2009-07-16 18:47 ` Frank Ch. Eigler
2009-07-16 8:16 ` Jakub Jelinek
2009-07-16 17:57 ` Ian Lance Taylor
2009-07-16 20:08 ` Zachary Turner
2009-07-17 9:00 ` Andrew Haley
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=E1MRRPM-00069A-P4@fencepost.gnu.org \
--to=ams@gnu.org \
--cc=aph@redhat.com \
--cc=divisortheory@gmail.com \
--cc=gcc@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).