Linux executable picks up FreeBSD library over linux one and breaks

[Chuck Robey]

Alex Dupre wrote:
> Chuck Robey wrote:
>> I guess I might be wrong, but I have to say, wrapping everything really
>> does seem to me to be the hack.
> 
> Call it a wrapper, call it a symlink, but it seems to me that you don't
> like linux libs in LOCALBASE *and* you don't like executable references
> in LOCALBASE (and these are the only two possibilities exposed by
> Alexander). I prefer the wrapper/symlink, because I think all linux
> stuff should be in /compat/linux. What do you propose, instead?
> 

(Until tomorrow, I won't be able to get my mail fixed to the point that 
my mail will get thru to hackers, but I will send this anyhow, in the 
hopes that maybe ...)

I'm sorry if I was not clear, I wish to do what hier(7) seems to be 
telling me. to put all linux executeables into the compat tree, into 
/compat, which is a symlink to /usr/compat, and underneath there, the 
correct name for each executable type, in this case into /compat/linux. 
  For example, llibraries would go into /compat/linux/usr/lib (realize 
that most Linux software ignores /usr/local/, I don't care for that, but 
if it's restricted to happening in /compat/linux then it's acceptable to 
me at least).  This makes for a single name that needs to go into 
linux's ldconfig list instread of the mess that's mismanaged now, and an 
equally simple setup for the linux PATH.  Easy was to segrregate all 
binaries, by their arch, nice and predictable, not needing to be 
extended for each new library.

This just seems like an obvioous thing to me, I'm sorry if I let that 
make me skip details.  No use oif LOCALBASE or LINUXBASE, unless you 
wanted to define LINUXBASE to be "linux" and then vector things into 
/compat/$(LINUXBASE), something like that would make sense.  But no use 
of LOCALBASE.

> --
> Alex Dupre
> _______________________________________________
> freebsd-hackers at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"