On Fri, Sep 23, 2011 at 10:02:07AM +0800, Bin Tian wrote:
Hi, all
On 2011年09月21日 22:06, Ian Lance Taylor wrote:
Stephen Kittst...@sk2.org writes:
Is there a recommended approach to use to find dlltool using only
i686-w64-mingw32-gcc?
I don't know of one. I don't know why avoiding
Hi, all
On 2011年09月21日 22:06, Ian Lance Taylor wrote:
Stephen Kittst...@sk2.org writes:
Is there a recommended approach to use to find dlltool using only
i686-w64-mingw32-gcc?
I don't know of one. I don't know why avoiding autoconf is desirable.
However, if I were forced to do so, I would
On 2011年09月23日 10:02, Bin Tian wrote:
Hi, all
On 2011年09月21日 22:06, Ian Lance Taylor wrote:
Stephen Kittst...@sk2.org writes:
Is there a recommended approach to use to find dlltool using only
i686-w64-mingw32-gcc?
I don't know of one. I don't know why avoiding autoconf is desirable.
Stephen Kitt st...@sk2.org writes:
Is there a recommended approach to use to find dlltool using only
i686-w64-mingw32-gcc?
I don't know of one. I don't know why avoiding autoconf is desirable.
However, if I were forced to do so, I would probably use gcc -v to get
the target name and look for
Hi,
I'm the current maintainer of the MinGW-w64-based gcc toolchain in
Debian. I've been asked (see http://bugs.debian.org/632003 for the
full discussion) to provide a method by which users may find the
appropriate dlltool to use, without using autoconf.
Some programs use --print-prog-name to
5 matches
Mail list logo