Intel ABI clarification

Brandon S. Allbery KF8NH (bsa@kf8nh.wariat.org)
Sat, 26 Aug 1995 18:13:20 -0400


In your message of Thu, 24 Aug 1995 12:42:06 EDT, you write:
+-----
| I don't think COFF extends across operating systems?? Syscalls and
| such are inherently non-portable.
+--->8

Correct. The iBCS module can *run* COFF executables. Linking is quite
another story; while syscalls aren't usually a problem (few COFF executables
use syscall(), instead making calls via libc), signal numbers, structure
sizes and offsets, and error numbers are not portable between native Linux
and iBCS. You must link iBCS libraries against an iBCS libc --- which
requires a linker with COFF support *and* an iBCS/COFF libc to link against.
You will also need an iBCS/COFF crt0.o and crtn.o.

++Brandon

-- 
Brandon S. Allbery	Linux & Solaris 2 hack; ham; soccer nut; pipe smoker
bsa@kf8nh.wariat.org	APK Net Ltd. *is* The Internet in Northern Ohio
bsa@telotech.com	Telotech, Inc., custom Unix database solutions