From: Daniel Jacobowitz <drow@false.org>
To: Masaki Muranaka <monaka@monami-software.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Failed to detect config.intl at sim/*/configure
Date: Mon, 12 Jun 2006 14:23:00 -0000 [thread overview]
Message-ID: <20060612142256.GA31885@nevyn.them.org> (raw)
In-Reply-To: <0E920490-41C1-4F87-A226-CFF4956569DE@monami-software.com>
On Mon, Jun 12, 2006 at 11:05:37PM +0900, Masaki Muranaka wrote:
> But... I feel this fix is slightly brute-forced.
> In case failed to create intl/config.intl, it's possible to
> detect config.intl which is out of the build tree.
> I hesitate I request to check this patch in.
This is true. However, autoconf does this in lots of places already,
and in these directories there should always be one or the other; we
now rely on configuring intl.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-06-12 14:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 5:07 Masaki Muranaka
2006-06-12 12:59 ` Daniel Jacobowitz
2006-06-12 14:05 ` Masaki Muranaka
2006-06-12 14:23 ` Daniel Jacobowitz [this message]
2006-06-12 15:27 ` Richard Earnshaw
2006-06-12 17:49 ` Richard Earnshaw
2006-06-12 18:51 ` Daniel Jacobowitz
2006-06-12 20:48 ` Alexandre Oliva
2006-06-13 6:55 ` Masaki Muranaka
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=20060612142256.GA31885@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=monaka@monami-software.com \
/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