Date: Thu, 26 Mar 1998 15:54:30 +0000 From: "Donald J.Maddox" <dmaddox@scsn.net> To: Tom <tom@uniserve.com>, Ollivier Robert <roberto@keltia.freenix.fr> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Linux binaries that don't run? Message-ID: <19980326155430.29791@scsn.net> In-Reply-To: <Pine.BSF.3.96.980325202535.7625F-100000@shell.uniserve.com>; from Tom on Wed, Mar 25, 1998 at 08:26:36PM -0800 References: <19980326002958.A10562@keltia.freenix.fr> <Pine.BSF.3.96.980325202535.7625F-100000@shell.uniserve.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 25, 1998 at 08:26:36PM -0800, Tom wrote: > > On Thu, 26 Mar 1998, Ollivier Robert wrote: > > > According to Tom: > > > ELF binaries need to be branded before use. ELF is a bit stupid in the > > > fact that it doesn't indicate what platform the binary is for. So you > > > need to use brandelf to write the type into the binary, so the loader > > > knows that it is Linux ELF. > > > > Nitpicking: that does concern only _static_ binaries. Dynamic have the > > loader's name encoded and don't need to be "branded". > > Strange. The original poster branded his binary, then ran into problems > because certain libraries couldn't be found. Sounds like dynically linked > to me :) In my experience, when you get a message that an ELF binary type is unknown when running a dynamically linked binary, it usually means that the message is caused not by the loading of the dynamic binary, but rather by that binary trying to load another that is _not_ dynamically linked. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980326155430.29791>