public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@codesourcery.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org,
	Jan Kratochvil <jan.kratochvil@redhat.com>,
	Joel Brobecker <brobecker@adacore.com>
Subject: Re: ping: [patch 5/6] testsuite: Fix prelink-support.exp without prelink installed
Date: Mon, 19 Jul 2010 15:43:00 -0000	[thread overview]
Message-ID: <20100719154257.GA26454@caradoc.them.org> (raw)
In-Reply-To: <201007191606.29992.pedro@codesourcery.com>

On Mon, Jul 19, 2010 at 04:06:29PM +0100, Pedro Alves wrote:
> On a related note: ubuntu/debian's system gdb includes some half cooked
> up gdb translations;

Just Ubunutu! :-)  I wasn't aware of these and they aren't in Debian.

> I then just remember to do "unset LANG", and rerun the testsuite,
> though I think this should be handled by our testsuite automatically
> somewhere.  How does gcc's testsuite handle this?

# We set LC_ALL and LANG to C so that we get the same error messages
as expected.
setenv LC_ALL C
setenv LANG C

-- 
Daniel Jacobowitz
CodeSourcery

  reply	other threads:[~2010-07-19 15:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-29 16:18 Jan Kratochvil
2010-06-09 15:10 ` ping: " Jan Kratochvil
2010-06-29 22:09   ` Joel Brobecker
2010-07-04 10:19     ` Jan Kratochvil
2010-07-05 17:40       ` Joel Brobecker
2010-07-05 18:13         ` Jan Kratochvil
2010-07-19 15:06       ` Pedro Alves
2010-07-19 15:43         ` Daniel Jacobowitz [this message]
2010-07-28 14:26           ` Disable i18n when running the testsuite (Re: ping: [patch 5/6] testsuite: Fix prelink-support.exp without prelink installed) Pedro Alves
2010-07-28 17:36             ` Joel Brobecker
2010-07-29 14:20               ` Disable i18n when running the testsuite Pedro Alves

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=20100719154257.GA26454@caradoc.them.org \
    --to=dan@codesourcery.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=pedro@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).