BSDi binary compatibility?
Maybe someone here knows. :-) I'm looking to compile a program that will ultimately run on a BSDi 2.1 machine. Are there any versions of FreeBSD that are capable of doing the compile and creating a compatible binary? (I've got FreeBSD releases since 2.0.5 stashed away). -- ... Joe --- Joe Greco - Systems Administrator [EMAIL PROTECTED] Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
BSDI binary compatibility
What kinds of BSDI binaries are we supposed to be able to run? I haven't had any luck getting *any* BSDI binaries to run on my (very recent) 4.0-CURRENT box. I have a handful of BSDI binaries, some of which are identified as: d...@des ~/yes/bsdi/shopsite% file wwwinstall.cgi wwwinstall.cgi: unknown pure executable d...@des ~/yes/bsdi/shopsite% ./wwwinstall.cgi zsh: bus error (core dumped) ./wwwinstall.cgi others (ls and cat from BSDI 4.0): d...@des ~/yes/bsdi/cmc% file ./ls ./ls: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically linked, stripped d...@des ~/yes/bsdi/cmc% ./ls ELF binary type not known. Use "brandelf" to brand it. zsh: abort ./ls and finally a few static ones Chris Costello was kind enough to build for me: d...@des ~/yes/bsdi/cmc/bsdi_static% file hello hello: ELF 32-bit LSB executable, Intel 80386, version 1, statically linked, not stripped d...@des ~/yes/bsdi/cmc/bsdi_static% ./hello ELF binary type not known. Use "brandelf" to brand it. zsh: abort ./hello DES -- Dag-Erling Smorgrav - d...@yes.no To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
BSDI binary compatibility
What kinds of BSDI binaries are we supposed to be able to run? I haven't had any luck getting *any* BSDI binaries to run on my (very recent) 4.0-CURRENT box. I have a handful of BSDI binaries, some of which are identified as: des@des ~/yes/bsdi/shopsite% file wwwinstall.cgi wwwinstall.cgi: unknown pure executable des@des ~/yes/bsdi/shopsite% ./wwwinstall.cgi zsh: bus error (core dumped) ./wwwinstall.cgi others (ls and cat from BSDI 4.0): des@des ~/yes/bsdi/cmc% file ./ls ./ls: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically linked, stripped des@des ~/yes/bsdi/cmc% ./ls ELF binary type not known. Use "brandelf" to brand it. zsh: abort ./ls and finally a few static ones Chris Costello was kind enough to build for me: des@des ~/yes/bsdi/cmc/bsdi_static% file hello hello: ELF 32-bit LSB executable, Intel 80386, version 1, statically linked, not stripped des@des ~/yes/bsdi/cmc/bsdi_static% ./hello ELF binary type not known. Use "brandelf" to brand it. zsh: abort ./hello DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BSDi binary compatibility?
In article <[EMAIL PROTECTED]>, Joe Greco <[EMAIL PROTECTED]> wrote: > Maybe someone here knows. :-) > > I'm looking to compile a program that will ultimately run on a BSDi 2.1 > machine. Are there any versions of FreeBSD that are capable of doing the > compile and creating a compatible binary? (I've got FreeBSD releases > since 2.0.5 stashed away). Yes, a.out static executables built under FreeBSD-2.2 will run under BSD/OS-3.x and -4.x at least. FreeBSD ELF executables won't work under BSD/OS, however, because along with the switch to ELF the system call mechanism was changed from "lcall 7,0" to the faster "int $0x80". BSD/OS doesn't support the latter, apparently. John -- John Polstra [EMAIL PROTECTED] John D. Polstra & Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BSDI binary compatibility
On Wed, Jul 21, 1999, Dag-Erling Smorgrav wrote: > and finally a few static ones Chris Costello was kind enough to build > for me: > > d...@des ~/yes/bsdi/cmc/bsdi_static% file hello > hello: ELF 32-bit LSB executable, Intel 80386, version 1, statically linked, > not stripped > d...@des ~/yes/bsdi/cmc/bsdi_static% ./hello > ELF binary type not known. Use "brandelf" to brand it. > zsh: abort ./hello FYI, I built them under 4.0.1 (if that matters). $ gcc -v gcc version 2.7.2.1 $ ld -v GNU ld version 2.8.1 (with BFD 2.8.1) $ as -v GNU assembler version 2.8.1 (bsd/os), using BFD version 2.8.1 > DES > -- > Dag-Erling Smorgrav - d...@yes.no > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-hackers" in the body of the message -- |Chris Costello |A bug in the code is worth two in the documentation. ` To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
Re: BSDI binary compatibility
On 21 Jul 1999, Dag-Erling Smorgrav wrote:
> What kinds of BSDI binaries are we supposed to be able to run? I
> haven't had any luck getting *any* BSDI binaries to run on my (very
> recent) 4.0-CURRENT box. I have a handful of BSDI binaries, some of
> which are identified as:
>
> d...@des ~/yes/bsdi/shopsite% file wwwinstall.cgi
> wwwinstall.cgi: unknown pure executable
> d...@des ~/yes/bsdi/shopsite% ./wwwinstall.cgi
> zsh: bus error (core dumped) ./wwwinstall.cgi
I Have some too, as such:
{"/home/green/ast/bin"}$ file ksh
ksh: BSD/OS i386 compact demand paged executable not stripped
{"/home/green/ast/bin"}$ ./ksh -c 'echo "Hello!"'
Hello!
>
> others (ls and cat from BSDI 4.0):
>
> d...@des ~/yes/bsdi/cmc% file ./ls
> ./ls: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically linked,
> stripped
> d...@des ~/yes/bsdi/cmc% ./ls
> ELF binary type not known. Use "brandelf" to brand it.
> zsh: abort ./ls
>
> and finally a few static ones Chris Costello was kind enough to build
> for me:
>
> d...@des ~/yes/bsdi/cmc/bsdi_static% file hello
> hello: ELF 32-bit LSB executable, Intel 80386, version 1, statically linked,
> not stripped
> d...@des ~/yes/bsdi/cmc/bsdi_static% ./hello
> ELF binary type not known. Use "brandelf" to brand it.
> zsh: abort ./hello
We aren't compatible with BSD/OS ELF in emulation. We've been compatible
with their a.out for years, but that's it. It's possible that if you
brandelf them to be of type "FreeBSD", they will work.
>
> DES
> --
> Dag-Erling Smorgrav - d...@yes.no
>
>
> To Unsubscribe: send mail to majord...@freebsd.org
> with "unsubscribe freebsd-hackers" in the body of the message
>
Brian Fundakowski Feldman _ __ ___ ___ ___ ___
gr...@freebsd.org _ __ ___ | _ ) __| \
FreeBSD: The Power to Serve!_ __ | _ \._ \ |) |
http://www.FreeBSD.org/ _ |___/___/___/
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
Re: BSDI binary compatibility
On Wed, Jul 21, 1999, Dag-Erling Smorgrav wrote: > and finally a few static ones Chris Costello was kind enough to build > for me: > > des@des ~/yes/bsdi/cmc/bsdi_static% file hello > hello: ELF 32-bit LSB executable, Intel 80386, version 1, statically linked, not >stripped > des@des ~/yes/bsdi/cmc/bsdi_static% ./hello > ELF binary type not known. Use "brandelf" to brand it. > zsh: abort ./hello FYI, I built them under 4.0.1 (if that matters). $ gcc -v gcc version 2.7.2.1 $ ld -v GNU ld version 2.8.1 (with BFD 2.8.1) $ as -v GNU assembler version 2.8.1 (bsd/os), using BFD version 2.8.1 > DES > -- > Dag-Erling Smorgrav - [EMAIL PROTECTED] > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- |Chris Costello <[EMAIL PROTECTED]> |A bug in the code is worth two in the documentation. ` To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BSDI binary compatibility
On 21 Jul 1999, Dag-Erling Smorgrav wrote:
> What kinds of BSDI binaries are we supposed to be able to run? I
> haven't had any luck getting *any* BSDI binaries to run on my (very
> recent) 4.0-CURRENT box. I have a handful of BSDI binaries, some of
> which are identified as:
>
> des@des ~/yes/bsdi/shopsite% file wwwinstall.cgi
> wwwinstall.cgi: unknown pure executable
> des@des ~/yes/bsdi/shopsite% ./wwwinstall.cgi
> zsh: bus error (core dumped) ./wwwinstall.cgi
I Have some too, as such:
{"/home/green/ast/bin"}$ file ksh
ksh: BSD/OS i386 compact demand paged executable not stripped
{"/home/green/ast/bin"}$ ./ksh -c 'echo "Hello!"'
Hello!
>
> others (ls and cat from BSDI 4.0):
>
> des@des ~/yes/bsdi/cmc% file ./ls
> ./ls: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically linked, stripped
> des@des ~/yes/bsdi/cmc% ./ls
> ELF binary type not known. Use "brandelf" to brand it.
> zsh: abort ./ls
>
> and finally a few static ones Chris Costello was kind enough to build
> for me:
>
> des@des ~/yes/bsdi/cmc/bsdi_static% file hello
> hello: ELF 32-bit LSB executable, Intel 80386, version 1, statically linked, not
>stripped
> des@des ~/yes/bsdi/cmc/bsdi_static% ./hello
> ELF binary type not known. Use "brandelf" to brand it.
> zsh: abort ./hello
We aren't compatible with BSD/OS ELF in emulation. We've been compatible
with their a.out for years, but that's it. It's possible that if you
brandelf them to be of type "FreeBSD", they will work.
>
> DES
> --
> Dag-Erling Smorgrav - [EMAIL PROTECTED]
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
>
Brian Fundakowski Feldman _ __ ___ ___ ___ ___
[EMAIL PROTECTED] _ __ ___ | _ ) __| \
FreeBSD: The Power to Serve!_ __ | _ \._ \ |) |
http://www.FreeBSD.org/ _ |___/___/___/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
