From: SourceForge.net <no...@so...> - 2004-10-06 02:06:02
|
Support Requests item #1040825, was opened at 2004-10-05 13:10 Message generated for change (Comment added) made by earnie You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=202435&aid=1040825&group_id=2435 Category: None Group: None Status: Open Priority: 5 Submitted By: Earnie Boyd (earnie) Assigned to: Danny Smith (dannysmith) Summary: Binutils bug? Initial Comment: I think the attached bugit.zip file represents a bug. Can you please confirm it? ---------------------------------------------------------------------- >Comment By: Earnie Boyd (earnie) Date: 2004-10-05 22:06 Message: Logged In: YES user_id=15438 Better error messages are always a good thing, however ld knows about the __imp__Foo symbol, it outputs it to libfoo.dll.a. Changing the make file to: <file name="Makefile"> CFLAGS = -O0 -g --save-temps all: exportFoo.o importFoo.o libfoo.dll exportFoo.o: exportFoo.c importFoo.o: importFoo.c libfoo.dll: importFoo.o exportFoo.o dlltool -l $@.a -D libfoo.dll $^ gcc -shared -o $@ $^ $@.a clean: rm -f *.o *.dll *.a *.i *.s </file> causes the creation of the dll. ---------------------------------------------------------------------- Comment By: Danny Smith (dannysmith) Date: 2004-10-05 20:19 Message: Logged In: YES user_id=11494 I don't know if it is a 'bug', but it may well be a feature that MS linker supports and ld doesn't. The importFoo code asks for __imp__Foo, but exportFoo only defines _Foo. I don't know how hard it would be to have ld fixup the unresolved symbol. Would you settle for just a better error message? Danny ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=202435&aid=1040825&group_id=2435 |