public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bin Tian <tianbin@cernet.edu.cn>
To: Ian Lance Taylor <iant@google.com>
Cc: Stephen Kitt <steve@sk2.org>,
	gcc-help@gcc.gnu.org,  632003@bugs.debian.org,
	 Bill Allombert <Bill.Allombert@math.u-bordeaux1.fr>
Subject: Re: Finding dlltool using gcc
Date: Fri, 23 Sep 2011 02:00:00 -0000	[thread overview]
Message-ID: <4E7BE89F.5020902@cernet.edu.cn> (raw)
In-Reply-To: <mcr62km7zxu.fsf@coign.corp.google.com>

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.

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?

Bin Tian

  reply	other threads:[~2011-09-23  2:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21  5:51 Stephen Kitt
2011-09-21 14:06 ` Ian Lance Taylor
2011-09-23  2:00   ` Bin Tian [this message]
2011-09-23  2:56     ` Bin Tian
2011-09-23 23:43     ` Bill Allombert
2011-09-26  9:07       ` Bug#632003: " Stephen Kitt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E7BE89F.5020902@cernet.edu.cn \
    --to=tianbin@cernet.edu.cn \
    --cc=632003@bugs.debian.org \
    --cc=Bill.Allombert@math.u-bordeaux1.fr \
    --cc=gcc-help@gcc.gnu.org \
    --cc=iant@google.com \
    --cc=steve@sk2.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).