This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Problem with static linking

From: fche at redhat dot com (Frank Ch. Eigler)
To: Andrew Haley <aph at redhat dot com>
Cc: Zachary Turner <divisortheory at gmail dot com>, gcc at gcc dot gnu dot org
Date: Thu, 16 Jul 2009 14:46:59 -0400
Subject: Re: Problem with static linking
References: <478231340907151937x4f1059f8l4545bb071441c9f9@mail.gmail.com> <4A5ED994.2010301@redhat.com>

Andrew Haley <aph@redhat.com> writes:

>> [...] It makes heavy use of
>> C++, STL, and boost and we'd like to (if possible) link *everything*
>> statically.  This means libc, libgcc, libstdc++, boost, libpthread,
>> etc.
> [...]
> 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.

If they actually encounter that ton of problems, then they will
change their minds about libc, regardless of preemptive imploring.


- FChE

References:
- Problem with static linking
  - From: Zachary Turner
- Re: Problem with static linking
  - From: Andrew Haley

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]