Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Masaki Muranaka <monaka@monami-software.com>
To: gdb-patches@sourceware.org
Cc: Daniel Jacobowitz <drow@false.org>
Subject: Re: Failed to detect config.intl at sim/*/configure
Date: Mon, 12 Jun 2006 14:05:00 -0000	[thread overview]
Message-ID: <0E920490-41C1-4F87-A226-CFF4956569DE@monami-software.com> (raw)
In-Reply-To: <20060612125826.GA28836@nevyn.them.org>


On 2006/06/12, at 21:58, Daniel Jacobowitz wrote:
> I couldn't see how either - we want $ac_top_builddir but the only way
> to set it is undocumented.  But, we can just keep trying.  Want to try
> this patch?

Thanks for your patch.
I've tried similar fix and it works well.

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.

The plan B is to create sim/intl/config.intl.
sim/intl/config.intl contains:
: #!/bin/sh
: . ../../intl/config.intl
This is more safety but it's a roundabout way.


BTW, I tried also ac_top_builddir like this.
: if test -f $ac_top_builddir/intl/config.intl; then ...
and it was failed because ac_top_builddir was empty.

--
Masaki Muranaka
Monami software



  reply	other threads:[~2006-06-12 14:05 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 [this message]
2006-06-12 14:23     ` Daniel Jacobowitz
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=0E920490-41C1-4F87-A226-CFF4956569DE@monami-software.com \
    --to=monaka@monami-software.com \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.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