Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!sdd.hp.com!caen!uwm.edu!linac!att!att!cbnewsl!urban
From: urban@cbnewsl.att.com (john.urban)
Newsgroups: comp.unix.sysv386
Subject: Re: Getting FAS to work with 3.2.2
Message-ID: <1991May7.141653.8379@cbnewsl.att.com>
Date: 7 May 91 14:16:53 GMT
References: <1991May7.022429.16710@cunixf.cc.columbia.edu>
Distribution: na
Organization: AT&T Bell Laboratories
Lines: 33

In article <1991May7.022429.16710@cunixf.cc.columbia.edu> puglia@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.  
>I have absolutely no idea which ELF file they are talking about. I have 
>set up the directories and the sdevices entry as I have done with other 
>drivers, but things just won't work.  I think that I have removed all 
>traces of the asy driver, but I can be 100% sure that that is not getting
>in the way.  Any suggestions would be greatly appreciated.
>

The UNIX System V/386 Release 3.2 Version 2.x Installable Drivers/Tuneable
Parameter feature only supports COFF (Common Object Format Files) Driver.o's.
The boot code will only boot a pure COFF kernel.  UNIX System V/386 Release 3.2
Version 2.2 does support limited ELF (Executable and Linking Format) executables
but not for kernel modules.

The compiler you're using to compile fas.c -> fas.o (then renamed to Driver.o)
is creating an ELF object file and not a COFF object file.  Type in:

# cd /etc/conf/pack.d
# file kernel/*.o fas/*.o

And look at the output.

You'll need to get the proper compiler for SVR3.2.x to create COFF based Driver.o
instead of ELF based.  Try using the AT&T CI4.1.5 or CI4.1.6 compiler.

Sincerely,

John Urban