From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28172 invoked by alias); 23 Sep 2011 02:56:28 -0000 Received: (qmail 28163 invoked by uid 22791); 23 Sep 2011 02:56:27 -0000 X-SWARE-Spam-Status: No, hits=-0.0 required=5.0 tests=BAYES_00,FH_HAS_XAIMC X-Spam-Check-By: sourceware.org Received: from sea.net.edu.cn (HELO cernet.edu.cn) (202.112.39.2) by sourceware.org (qpsmtpd/0.43rc1) with SMTP; Fri, 23 Sep 2011 02:56:12 +0000 Received: from [192.168.0.129]([127.0.0.25]) by cernet.edu.cn(AIMC 3.2.0.0) with SMTP id jm04e7c693e; Fri, 23 Sep 2011 10:56:06 +0800 Message-ID: <4E7BF5CC.4080502@cernet.edu.cn> Date: Fri, 23 Sep 2011 02:56:00 -0000 From: Bin Tian User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2 MIME-Version: 1.0 To: Ian Lance Taylor CC: Stephen Kitt , gcc-help@gcc.gnu.org, 632003@bugs.debian.org, Bill Allombert Subject: Re: Finding dlltool using gcc References: <20110921055036.GE7506@sk2.org> <4E7BE89F.5020902@cernet.edu.cn> In-Reply-To: <4E7BE89F.5020902@cernet.edu.cn> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-AIMC-AUTH: tianbin X-AIMC-MAILFROM: tianbin@cernet.edu.cn X-AIMC-Msg-ID: q3qvvG1B Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2011-09/txt/msg00187.txt.bz2 On 2011年09月23日 10:02, Bin Tian wrote: > Hi, all > > On 2011年09月21日 22:06, Ian Lance Taylor wrote: >> Stephen Kitt 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. > > autoconf should be the proper way, because it deals with more > circumstances. Any other attempts will be reinventing the wheel. > > If autoconf is not desirable, we should try to find it in autoconf's > way, try $target-dlltool first and dlltool next. > >> >>> I am wrong in dropping /usr/$target/bin? >> >> No, you are right. That directory is used to communicate programs from >> the binutils to gcc, and there are no promises about what binaries may >> be found there. >> > > Despite the fact I submit the bug, I think this isn't a bug. > > We could do nothing and just wait multiarch to be ready. There will be > dlltool in /usr/$target/bin, isn't it? sorry I'm wrong. /usr/$target/bin contains programs running on $target, this isn't true for cross-compiling toolchains. > > Bin Tian