Oh yes that's what has happened, I checked the symbols with "nm driver2" and the driver1 symbols no longer appear as UNDEF. But that is not what I want.
OK so here's what happens when I use your option of ld -dy -N /kernel/drv/driver1 -N /kernel/misc/scsi -r driver2.o -o driver2 Upon loading driver2, it doesn't attach although driver1 is loaded and attached already. Would you know why this is happening? It also seems like from the dmesg output that driver2 is no longer complaining about either driver1 or transport layer symbols, as I'm getting no error messages. So I'm not sure why attach isn't being called now but of course it succeeds when I use -Bdirect. Regards, Bhaskar. -----Original Message----- From: cas...@holland.sun.com [mailto:cas...@holland.sun.com] On Behalf Of casper....@sun.com Sent: Monday, August 31, 2009 2:49 PM To: Jayaraman, Bhaskar Cc: opensolaris-code@opensolaris.org Subject: Re: [osol-code] Exporting solaris symbols from driver! >Yes that's correct, driver1 is present in /kernel/drv and driver2 has symbols >it is using from dri ver1 and also transport layer functions. > The -Bdirect option seems to be working fine though. Wel, if you actually used the command line as before: >ld -dy -Bdirect driver1 -r driver2.o -o driver2 (and you used "driver1" here as argument after -Bdirect) then you've linked driver1 into driver2. Casper _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
