Re: broken linuxulator in -current as of Jan 8 17:51:45 CET

On Mon, Jan 08, 2007 at 08:32:03PM +0300, Boris Samorodov wrote:
On Mon, 8 Jan 2007 17:51:57 +0100 Divacky Roman wrote:

can someone confirm that running for example /bin/ls
in linux compat doesnt work. here it goes like:

witten ~# /compat/linux/bin/ls
/compat/linux/bin/ls: error while loading shared libraries: /usr/lib/librt.so.1: ELF file OS ABI invalid

I don't have -current ATM, but if you won't find an error at your
config, I'll definitely do.

I didnt change anything... it just stopped working :( I am doing
non-fbsd work these days so I really cannot imagine what changed

I cannot see what can be wrong. I tried to backout all changes that
alexander commited yesterday but it didnt help. is it regression
local to my machine or is the problem -current wide?

/usr/ports/UPDATING (20060616: AFFECTS users of emulation/linux_base-*)
has some advices how to find and diagnose the culprit. The most
typical case here is changing the standard way of library searching
(i.e. LD_* paths, etc.).

I dont have anything like that set... it looks like a bug in kernel/linux_base
because the trace looks like:

Jan 8 18:57:59 witten kernel: linux(1582): open(/lib/tls/librt.so.1, 0x0, 0x0)
Jan 8 18:57:59 witten kernel: linux(1582): open returns error 2
Jan 8 18:57:59 witten kernel: linux(1582): open(/compat/linux/lib/librt.so.1, 0x0, 0x0)
Jan 8 18:57:59 witten kernel: linux(1582): open returns error 0
Jan 8 18:57:59 witten kernel: linux(1582): open(/usr/lib/tls/librt.so.1, 0x0, 0x0)
Jan 8 18:57:59 witten kernel: linux(1582): open returns error 2
Jan 8 18:57:59 witten kernel: linux(1582): open(/usr/lib/librt.so.1, 0x0, 0x0)
Jan 8 18:57:59 witten kernel: linux(1582): open returns error 0
Jan 8 18:57:59 witten kernel: linux(1582): exit_group(127)

ie. it opens the right library but IGNORES it and the iterates through the rest
and then stops on fbsd library saying that its not compatible...

from within jail it works (because it must stop at the correct library). I tried
to reinstall fc4 base but it didnt help. I see this behaviour on both fc4 and gentoo
base. I even tried to cvsup to yesterdays sources (when it worked for me) but it
didnt help either.. I am really hopeless ;(

roman
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"