[prev in list] [next in list] [prev in thread] [next in thread]
List: binutils
Subject: Re: stdcall, @s, and ld/dlltool...
From: "Dmitry Timoshkov" <dmitry () baikal ! ru>
Date: 2001-12-25 15:48:30
Message-ID: 002101c18d5b$bdb969f0$d1823bd5 () dmitry
[Download RAW message or body]
"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.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic