From: "Orson Cart" <ex-privat@parts.org>
Reply-To: "Orson Cart" <ex-privat@parts.org>
Subject: will linker choose static before dynamic library?
Newsgroups: comp.os.linux.development.apps
NNTP-Posting-Host: $$5emnja$xifvw3_n.feeder.x-privat.org
Message-ID: <4f5b2f79$1@x-privat.org>
Date: 10 Mar 2012 11:39:53 +0100
Organization: X-Privat NNTP Server - http://www.x-privat.org
Lines: 11
X-Authenticated-User: $$xs-7_q6xz085nc1qk
X-Complaints-To: abuse@x-privat.org
Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!newsfeed.x-privat.org!x-privat.org!not-for-mail
Xref: csiph.com comp.os.linux.development.apps:456


I was trying to build a supposedly well-behaved package, and got lots
of undefined reference errors.
The reason was that I had libX11.a from an attempt to build a crap
package that uses this obsolete library.
Now I also have libX11.so, so I renamed libX11.a and retried the
make.
All goes smoothly!
So if a developer assumes they are using the .so library,
do they get bitten, or can they use flags to shun the static relic?