Getting FAS to work with 3.2.2

john.urban urban at cbnewsl.att.com
Thu May 9 05:31:58 AEST 1991


In article <tim.673689050 at holly> tim at dell.co.uk (Tim Wright) writes:
>In <1991May07.144626.11638 at chinet.chi.il.us> randy at chinet.chi.il.us (Randy Suess) writes:
>
>>In article <1991May7.022429.16710 at cunixf.cc.columbia.edu> puglia at cunixf.cc.columbia.edu writes:
>>]Has anybody gotten FAS to work with ATT 3.2.2?  I can get the fas.c program
>>]to compile, but have been unable to get the kernel to link after I add
>>]the entry for it in the sdevices file.  The kernel linking process fails with
>>]the message:
>>]ld: Driver.o cannot open ELF file.  
>
>>	Sounds like you are trying to compile with the "Standard"
>>	development system, which is their ANSI compiler meant for
>>	sysvr4.  R4 uses ELF, not COFF format for linking.  You need the 
>>	"C software development set 4.1.?", which is the standard compiler 
>>	most other UNIX's use.
>
>No.
>AT&T 3.2.2 (note the last 2) has ELF binaries, not COFF. Hence the development

perhaps this is true for the 3b2 or anohter non-386 box.

>system is SCDE 5, not 4.1. It sounds more like he's installed fas.o instead
>of renaming it to Driver.o ?
>
>Tim

AT&T UNIX System V/386  Release 3.2 Version 2.2 'supports' ELF binaries in
a limited way.  However the kernel boot code only supports only a COFF kernel
and not a ELF or COFF/ELF kernel.  Also the Installabel Driver/Tuneable Parameter
feature only supports COFF Driver.os.

Therefore, inorder to get FAS to work on AT&T UNIX System V/386 Release 3.2
Version 2.2, you must have a SCDE 4.1.5 or SCDE 4.1.6.

AT&T does offer a CI5/3 which is a ELF compiler for UNIX System V/386 Release
3.2 Version 2.2, but if you create Driver.o's with this you will not be able to
link-edit them into you 3.2.2 kernel.

If the user, forgot to move the file from fas.o to Driver.o, I don't think
he would see: "ld: Driver.o cannot open ELF file". but some other message
about missing Driver.o.

Perhaps the original poster can type in: file Driver.o /unix and let us all
know what the answers are.


Sincerely,
John Ben Urban



More information about the Comp.unix.sysv386 mailing list