Date: Tue, 15 Oct 1996 11:33:42 +0200 (MET DST) From: sos@FreeBSD.org To: msmith@atrad.adelaide.edu.au (Michael Smith) Cc: hackers@FreeBSD.org Subject: Re: Linux compat issue(s) Message-ID: <199610150933.LAA13406@ra.dkuug.dk> In-Reply-To: <199610150917.SAA21553@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Oct 15, 96 06:47:32 pm
next in thread | previous in thread | raw e-mail | index | archive | help
In reply to Michael Smith who wrote:
>
> The failing applications don't actually even raise a peep from the
> Linux emulator. Here we have 'lmgrd' (works) and 'lmclient' (fails) :
>
> rootvegetable:/local0/gsi/flexlm/v5.0/i86_l1>file lmgrd lmclient
> lmgrd: ELF 32-bit LSB executable, Intel 80386, version 1
> lmclient: ELF 32-bit LSB executable, Intel 80386, version 1
> rootvegetable:/local0/gsi/flexlm/v5.0/i86_l1>/compat/linux/usr/bin/ldd lmgrd lmclient
> lmgrd:
> libc.so.5 => /lib/libc.so.5.0.9
> lmclient:
> statically linked (ELF)
>
>
> Should I assume that this is the "what static ELF binary is this" problem?
Exactly, the static ELF program is run as a FreeBSD native bin, there
is no way to know better (yet).
I guess we'll have to provide a solution for this shortcoming in
ELF (WHO said ELF was "the way to go" *sigh*)
I can do a "quick&dirty"(tm) little program that marks ELF bins so that
we can distinguish them, but it breaks the ELF std. one way or another.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team
So much code to hack -- so little time.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610150933.LAA13406>