From owner-freebsd-current  Wed Mar 25 10:26:30 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA01726
          for freebsd-current-outgoing; Wed, 25 Mar 1998 10:26:30 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA01721
          for <freebsd-current@freebsd.org>; Wed, 25 Mar 1998 10:26:27 -0800 (PST)
          (envelope-from tom@uniserve.com)
Received: from shell.uniserve.com [204.244.186.218] 
	by pop.uniserve.com with smtp (Exim 1.82 #4)
	id 0yHurv-0007Kr-00; Wed, 25 Mar 1998 10:25:43 -0800
Date: Wed, 25 Mar 1998 10:25:41 -0800 (PST)
From: Tom <tom@uniserve.com>
To: Alex Le Heux <alexlh@funk.org>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: Linux binaries that don't run?
In-Reply-To: <19980325104506.60902@p.funk.org>
Message-ID: <Pine.BSF.3.96.980325102305.27923A-100000@shell.uniserve.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On Wed, 25 Mar 1998, Alex Le Heux wrote:

> ELF binary type not known

  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.

  Apparently, some ELF binaries are branded before you get them.

Tom


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message