This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: stdcall, @s, and ld/dlltool...
- From: "Dmitry Timoshkov" <dmitry at baikal dot ru>
- To: "Matthew Brett" <matthew dot brett at mrc-cbu dot cam dot ac dot uk>
- Cc: <binutils at sources dot redhat dot com>
- Date: Tue, 25 Dec 2001 23:48:30 +0800
- Subject: Re: stdcall, @s, and ld/dlltool...
- References: <Pine.GSO.4.21.0112251342060.7017-100000@sabik>
"Matthew Brett" <matthew.brett@mrc-cbu.cam.ac.uk> wrote:
> Many thanks for the reply. Suffering as I have from this problem, I had
> found your messages on this list, which was why I reposted here. I have
> the painful feeling I don't understand this problem completely, but my
> worry is that I can't use this solution:
>
> > dllwrap -o $(LIBRARY).dll $(OBJS) $(LIBS) -k --def $(LIBRARY).def ...
>
> because I do not have the source for the libraries. It is true isn't it
> that for some reason --enable-stdcall-fixup when doing final linking with
> the dll library created by dlltool, does not work on this problem? Is
> this a bug?
Oh, sorry. Didn't pay enough attention to your post. But anyway, you might
create a proper import library to link with, and in that case patched dlltool
should help you here:
dlltool --kill-at --input-def $(LIBRARY).def --output-lib lib$(LIBRARY).a
--
Dmitry.