From: Ian Lance Taylor <iant@google.com>
To: Stephen Kitt <steve@sk2.org>
Cc: gcc-help@gcc.gnu.org, 632003@bugs.debian.org,
Bin Tian <tianbin@cernet.edu.cn>,
Bill Allombert <Bill.Allombert@math.u-bordeaux1.fr>
Subject: Re: Finding dlltool using gcc
Date: Wed, 21 Sep 2011 14:06:00 -0000 [thread overview]
Message-ID: <mcr62km7zxu.fsf@coign.corp.google.com> (raw)
In-Reply-To: <20110921055036.GE7506@sk2.org> (Stephen Kitt's message of "Wed, 21 Sep 2011 07:50:36 +0200")
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.
> 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.
Ian
next prev parent reply other threads:[~2011-09-21 14:06 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 [this message]
2011-09-23 2:00 ` Bin Tian
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=mcr62km7zxu.fsf@coign.corp.google.com \
--to=iant@google.com \
--cc=632003@bugs.debian.org \
--cc=Bill.Allombert@math.u-bordeaux1.fr \
--cc=gcc-help@gcc.gnu.org \
--cc=steve@sk2.org \
--cc=tianbin@cernet.edu.cn \
/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).