2010/9/10 Xiaofan Chen <xiaof...@gmail.com>:
> On Fri, Sep 10, 2010 at 3:29 PM, Ozkan Sezer <seze...@gmail.com> wrote:
>>>> gcc -o libusb0.sys abort_endpoint.o claim_interface.o clear_feature.o 
>>>> dispatch.o
>>>>  get_configuration.o get_descriptor.o get_interface.o get_status.o ioctl.o 
>>>> libus
>>>> b_driver.o pnp.o release_interface.o reset_device.o reset_endpoint.o 
>>>> set_configu
>>>> ration.o set_descriptor.o set_feature.o set_interface.o transfer.o 
>>>> vendor_reques
>>>> t.o power.o driver_registry.o error.o libusb_driver_rc.o  libusb0_drv.def 
>>>> -s -sh
>>>> ared -Wl,--entry,_driveren...@8 -nostartfiles -nostdlib -L. -lusbd 
>>>> -lntoskrnl -l
>>>> hal
>>>> d:/tdm/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/4.5.1/../../../../x86_64-w64-mi
>>>> ngw32/bin/ld.exe: warning: cannot find entry symbol _driveren...@8; 
>>>> defaulting t
>>>> o 0000000068641000
>>>
>>> Don't know this one ...
>>>
>>
>> One note here that just crossed my mind:  why are you using a __stdcall 
>> suffix
>> DriverEntry, _and_ you are adding a leading underscore to it?
>
> That is probably because of the code was written for MinGW.org GCC.
> Remove the leading underscore (--> driveren...@8) fixed this.
>
>
> --
> Xiaofan
>

Well, for 64-bit this @8 is pretty superflous and should be removed,
too. ld kills is - as it is so clever - but in fact is an error, as
there is no such stdcall decoration on 64-bit windows.

Kai

-- 
|  (\_/) This is Bunny. Copy and paste
| (='.'=) Bunny into your signature to help
| (")_(") him gain world domination

------------------------------------------------------------------------------
Automate Storage Tiering Simply
Optimize IT performance and efficiency through flexible, powerful, 
automated storage tiering capabilities. View this brief to learn how
you can reduce costs and improve performance. 
http://p.sf.net/sfu/dell-sfdev2dev
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to