guy keren <[EMAIL PROTECTED]> writes:

> actually, this is easier then it sounds. all you need to do is make sure
> processes linked with different libraries, look for them in different
> directories. this can be done either during compile (actually link) time,
> with the '-rpath' switch of gnu ld, or during run time, with
> LD_LIBRARY_PATH.  

I already had the binaries, so I only needed run-time.

As I indicated in my original posting, there was some inconsistency
that I could not immediately resolve. I could run 

# LD_LIBRARY_PATH=/lib ls

etc (but I could not substitute scripts or alias them all), but with
the default LD_LLIBRARY_PATH (/lib:/usr/lib) I could not run "new"
programs setting LD_LIBRARY_PATH to the location of the _newer_
libraries in an obvious way. The reason was that libc.so.6 was still
searched for in /lib, and that pointed to GLIBC_2.2.2, whereas
binutils were dependent on GLIBC_2.2.3.

One suggestion was that somehow ldconfig was the culprit, and I should
check that. I never followed up on that, because meanwhile I got
assured by the vendor that I could installpkg stuff from slack-8.0,
effectively upgrading the libraries.

Before that, I had thought of going the route of compiling just
about everything there (I did it enough times to not be afraid of it),
but binutils is a prerequisite for compiling anything, and I did not
have a good algorithm for looking for a compatible binary.

So the brute force way to go was cross-compiling glibc (since I needed
the include files for cross-compiling), then cross-compiling binutils,
gcc, etc, and hoping for the best. That's more hairy.

I would have checked ldconfig first, just to be sure.

-- 
Oleg Goldshmidt | [EMAIL PROTECTED] 
[Lisp] is the only computer language that is beautiful. 
                      - Neal Stephenson 

=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Reply via email to