From owner-freebsd-current Wed Apr 1 12:57:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA10092 for freebsd-current-outgoing; Wed, 1 Apr 1998 12:57:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from p.funk.org (p.funk.org [194.109.86.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA10085 for ; Wed, 1 Apr 1998 12:57:11 -0800 (PST) (envelope-from alexlh@xs4all.nl) Received: from xs4all.nl (localhost [127.0.0.1]) by p.funk.org (8.8.8/8.8.8) with ESMTP id WAA01568; Wed, 1 Apr 1998 22:56:00 +0200 (CEST) (envelope-from alexlh@xs4all.nl) Message-ID: <3522A9E0.A8B1915@xs4all.nl> Date: Wed, 01 Apr 1998 20:56:00 +0000 From: Alex Le Heux X-Mailer: Mozilla 4.04 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: dmaddox@scsn.net, freebsd-current@FreeBSD.ORG Subject: Re: Linux binaries that don't run? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Donald J.Maddox wrote: > > 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. What actually happened is that the first binary (needed to be branded first) _did_ start a second, which had to be branded as well, and then died because it could not find some libraries.... Alex -- A computer without Windows is like a fish without a bicycle. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message