This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Finding dlltool using gcc

From: Bill Allombert <Bill dot Allombert at math dot u-bordeaux1 dot fr>
To: Bin Tian <tianbin at cernet dot edu dot cn>
Cc: Ian Lance Taylor <iant at google dot com>, Stephen Kitt <steve at sk2 dot org>, gcc-help at gcc dot gnu dot org, 632003 at bugs dot debian dot org
Date: Fri, 23 Sep 2011 21:03:24 +0200
Subject: Re: Finding dlltool using gcc
References: <20110921055036.GE7506@sk2.org> <mcr62km7zxu.fsf@coign.corp.google.com> <4E7BE89F.5020902@cernet.edu.cn>

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 Kitt<steve@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 TARGET-dlltool that way.
> gcc -dumpmachine is more relavant.

Yes, gcc -dumpmachine reports the right value, thanks a lot for the suggestion.

> autoconf should be the proper way, because it deals with more
> circumstances. Any other attempts will be reinventing the wheel.

The configure system of the software in case predates autoconf by a large margin.

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here.

Follow-Ups:
- Re: Bug#632003: Finding dlltool using gcc
  - From: Stephen Kitt

References:
- Finding dlltool using gcc
  - From: Stephen Kitt
- Re: Finding dlltool using gcc
  - From: Ian Lance Taylor
- Re: Finding dlltool using gcc
  - From: Bin Tian

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]