Casper Hornstrup wrote:
Is the command line wrong?
Casper
I don't see this problem on an old cache manager branch. On the trunk,
it is running dlltool and ld. On the cache manager branch, it is running
ld, dlltool and ld.
trunk:
dlltool --dllname atapi.sys --def tools\rbuild\empty.def --output-exp
atapi.temp.exp --kill-at
gcc -Wl,--subsystem,native -Wl,--entry,_DriverEntry@8
-Wl,--image-base,0x00010000 -Wl,--file-alignment,0x1000
-Wl,--section-alignment,0x1000 -nostartfiles -shared atapi.temp.exp -o
.\up\output-i386\drivers\storage\atapi\atapi.sys
.\up\obj-i386\drivers\storage\atapi\atapi.o
.\up\obj-i386\drivers\storage\atapi\atapi.coff
.\up\obj-i386\ntoskrnl\libntoskrnl.a .\up\obj-i386\hal\hal\libhal.a
.\up\obj-i386\drivers\storage\scsiport\libscsiport.a -g -nostartfiles
-nostdlib
What version of binutils are you using? (for reference)
I guess this is result of one of my old attempt to simplify the three
step linking ... Ideally DLLTOOL shouldn't be used at all and then
everything works fine, but that depends on patch to LD that isn't part
of the official bintutils yet (I've been waiting few months for getting
the copyright assignment papers sorted out :/). I'll probably look at it
on the weekend.
- Filip