Very Computer

by **Mark H. Wo** » Sun, 08 Oct 1995 04:00:00

The stock libXpm.3.4f-ELF.tar.gz places the files in [/]usr/X11R6/lib. The
stock GCC 2.7.0 kit includes ld scripts that don't look there. Much (but not
all) of the stuff in XFree86 3.1.x gets symlinked from places where the ld
scripts *do* look, so some things link and some don't depending on which
libraries they want. This will drive you crazy until you realize that ld isn't
using the same search list as ld.so.

Is it better to make (and maintain) scads of symlinks for all these libraries,
or to tweak the ld scripts to look in *all* of the "right places"? From a
maintenance standpoint, I'd rather the latter, but I wanted a reality check
before doing so.
--

You are in a twisty little maze of hyperlinks, all useless.

by **Mark H. Wo** » Tue, 10 Oct 1995 04:00:00

Hmmm, I could have been more specific. gcc 2.7.0 searches for libraries only
in /lib:/usr/lib:/usr/local/lib:/usr/i486-linux/lib and nowhere else, according
to the stuff in /usr/lib/ldscripts/*. Any X libraries that are found by
default, are found because each such library has been linked from one of those
directories. Is it worth bugging H.J. to add, say, /usr/X11/lib to the
standard SEARCH_DIR list? Then only the /usr/X11 link needs to be maintained
as we upgrade X. This should eliminate a lot of questions about "the linker
claims it can't find libTHUSANDSO, but it is there...".

You could argue that the X stuff should live in the "standard" library
directories with everything else, but there are relationships among the X
libraries that are much stronger than among most collections of libraries, and
I can see why we'd want to keep them segregated. Comments?

(BTW, anybody know what's up with the FSSTND document? The server keeps saying
404 Not Found....)
--

You are in a twisty little maze of hyperlinks, all useless.

Very Computer

Another way ld can fail to find e.g libXpm.so

Another way ld can fail to find e.g libXpm.so

Another way ld can fail to find e.g libXpm.so