Very Computer

All,

I am sure an easy question (newbie) but I am trying to compile SUN's
ramdisk example driver, with:

cc -O -I/net/devi/usr/include -I. -D_KERNEL    -c -o /ramdisk.o
ramdisk.c
ld -r -o /ramdisk /ramdisk.o
cc -O -I/net/devi/usr/include -I. -D_KERNEL    -I/net/devi/usr/include
-I.   ramdisk.c /ramdisk   -o ramdisk
ld: fatal: symbol `_init' is multiply defined:
        (file /opt/SUNWspro/WS6U1/lib/crti.o and file ramdisk.o);
ld: fatal: symbol `_fini' is multiply defined:
        (file /opt/SUNWspro/WS6U1/lib/crti.o and file ramdisk.o);
ld: fatal: symbol `_init' is multiply defined:
        (file /opt/SUNWspro/WS6U1/lib/crti.o and file /ramdisk);
ld: fatal: symbol `_info' is multiply defined:
        (file ramdisk.o and file /ramdisk);
ld: fatal: symbol `_fini' is multiply defined:
        (file /opt/SUNWspro/WS6U1/lib/crti.o and file /ramdisk);
ld: fatal: File processing errors. No output written to ramdisk
make[1]: *** [ramdisk] Error 1
make[1]: Leaving directory `/opt/SUNWddk/src/drivers/ramdisk'
make: *** [ramdisk] Error 2

It looks like the crt library is getting pulled in, which will not work
for kernel space.

What is up, and how can I fix it?

Thx In Adv.

Why are you compiling ramdisk.c again?  You are done after the link.

Yep.

The second "cc" line is using cc (the compiler front end)
to do a compile and link with a single command
line.  Because you're using cc to invoke the link it assumes you
want a standalone executable and automatically includes crt and
several other libraries in the linker command line it generates
under the covers.  Most cc's
have a command line option to show you all the command lines
generated to get the job done.

The first two lines are all you need, the third command line
is unnecessary and does the wrong things for a driver.

-- Doug

BTW, you are probably already aware of this, but just in case:

[[ PLEASE DON'T SEND ME EMAIL COPIES OF POSTINGS ]]

This gets you ramdisk.o

Quote:>ld -r -o /ramdisk /ramdisk.o

And here you are done.

(Uhm, you're not really compiling in /, are you?

Quote:>cc -O -I/net/devi/usr/include -I. -D_KERNEL    -I/net/devi/usr/include
>-I.   ramdisk.c /ramdisk   -o ramdisk

Looks like a second compile, this time to an application. This brings
in the runtime startup glue which you don't want.

Compile to .o and then link with ld.

Casper
--
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

Just out of curiosity, where do you get this ramdisk.c example code?