* Using foo in statically linked ...
@ 2004-01-19 21:02 Gary Cote
0 siblings, 0 replies; only message in thread
From: Gary Cote @ 2004-01-19 21:02 UTC (permalink / raw)
To: gcc-help
My quest to port our system from gcc 2.96 to gcc 3.2.3 continues.
I'm now trying to resolve link errors. I'm getting a bunch of
messages that take the form:
Using 'foo' in statically linked applications requires
at runtime the shared libraries from the glibc version used
for linking.
Where foo is one of many library calls (e.g. getpwnam,
getservbyname, etc.)
Ok ... so what's the deal here? If I'm linking statically,
why does it need the glibc shared libs? Am I prohibited
from linking certain libs statically?
For that matter, what exactly is the significance of this
message? Is it just a helpful hint? Or a warning? Or an
error? What's it take to make this go away?
--
Gary Cote
gcote@transat-tech.com
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-01-19 21:02 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-01-19 21:02 Using foo in statically linked Gary Cote
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).