On Mon, May 20, 2002 at 05:30:50PM +0100, Nick Ing-Simmons wrote:
> Bill Moseley <[EMAIL PROTECTED]> writes:

> BSD may still be using a traditional "a.out" object format which does
> not have the hooks (e.g. SunOS also used to fail this sort of thing.)

> >On FreeBSD 4.5 with 5.005_03 it always aborts (regardless of PERL_DL_NONLAZY).

> exceptions have been subject to radical re-design in gcc - if your free bsd
> machine has as old a gcc as it has a a perl chances are exceptions just 
> don't work right at all.

$ uname -a
FreeBSD thinking-cap.moo 4.5-STABLE FreeBSD 4.5-STABLE #1: Wed Feb  6 16:15:14 GMT 
2002     [EMAIL PROTECTED]:/stuff/usr/src/sys/compile/THINKINGCAP  i386
$ gcc -v
Using builtin specs.
gcc version 2.95.3 20010315 (release) [FreeBSD]
$ file /usr/bin/perl
/usr/bin/perl: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), 
dynamically linked (uses shared libs), stripped


While on Debian here I have:
$ gcc -v
Reading specs from /usr/lib/gcc-lib/arm-linux/2.95.4/specs
gcc version 2.95.4 20010319 (Debian prerelease)
$ file /usr/bin/perl
/usr/bin/perl: ELF 32-bit LSB executable, Advanced RISC Machines ARM, version 1, 
dynamically linked (uses shared libs), stripped

(and x86 should be just the same)
I don't know if FreeBSD and Linux use the same x86 ABI (particularly for
C++ exceptions) and (obviously) FreeBSD isn't using glibc.

(I realise this doesn't suggest how to cure the problem - it's more just to
say that the release of the BSD Bill is using is pretty close in most way
to Debian, hence the problem can only be in a few specific differences)

Nicholas Clark
-- 
Even better than the real thing:        http://nms-cgi.sourceforge.net/

Reply via email to