Date: Thu, 25 Jul 1996 14:42:38 -0700 (PDT) From: Mostyn/Annabella <mrl@teleport.com> To: chuckr@Glue.umd.edu (Chuck Robey) Cc: current@freebsd.org Subject: Re: Current, elfkit, linux ELF static bin Message-ID: <199607252142.OAA06919@linda.teleport.com> In-Reply-To: <Pine.OSF.3.91.960725164830.8213D-100000@modem.eng.umd.edu> from "Chuck Robey" at Jul 25, 96 04:54:44 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > On Thu, 25 Jul 1996, Mostyn/Annabella wrote: > > > Howdy, > > > > Running current with elfkit set up to provide /usr/libexec/ld-elf.so.1 > > seems to run hand rolled ELF bins fine. > > However, importing an ELF linux static bin and running (after installing > > the linux lkm) bombs. > > The binary is the "Bulldozer" WYSIWYG HTML editor from > > http://cscsun1.larc.nasa.gov/~rboykin/Dozer/ > > > > Running it gets > > > > ./dozer > > Memory fault (core dumped) > > > > and produces a "garbled" directory which looks like > > > > drw-r----- 2 root wheel 512 Jul 23 15:45 <V?o/ > > > > The ld-elf.so.1 is only for linux executeables that are dynamically > linked. When you do a 'file Bulldozer' (assuming that's the name of your > executeable) what does FreeBSD tell you (what type of file is it really?) Thanks, I was aware of the dynamic loader - I was imprecise - statically linked ELF bins made locally work too. I was only pointing out that it seems the kernel image activator for ELF seemed to be working OK. The "dozer" file, by the way, owns up to being -> file dozer dozer: ELF 32-bit LSB executable, Intel 80386, version 1 Mostyn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607252142.OAA06919>