From: Daniel Jacobowitz <drow@false.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] fix issues in some locales with using a-z
Date: Thu, 06 Jul 2006 13:32:00 -0000 [thread overview]
Message-ID: <20060706133243.GD18827@nevyn.them.org> (raw)
In-Reply-To: <200606220005.43029.vapier@gentoo.org>
On Thu, Jun 22, 2006 at 12:05:42AM -0400, Mike Frysinger wrote:
> a bunch of files in gdb use a-z in sed expressions without forcing the locale
> to c ... in some locales, this can cause some pretty "fun" results:
>
> (observer.sh)
> In file included from solib.c:47:
> observer.h:35: error: stray '@' in program
> observer.h:35: error: expected ')' before 'deftypefun'
>
> (Makefile.in:init.c)
> libgdb.a(init.o): In function `initialize_all_files':
> init.c:(.text+0xa): undefined reference to `_initialize_amd64_lin'
> init.c:(.text+0xf): undefined reference to `_initialize_i386_'
>
> i've fixed this issue in the Makefile.in, gdb_indent.sh, gdb_mbuild,sh, and
> observer.sh files the same way that gdbarch.sh was fixed oh-so-long ago
> rather than the over-the-top way that autoconf does it (see the top of
> gdb/configure under "NLS nuisances" to see what i mean)
Tsk tsk. You must not have tested this patch too well; you made the
mistake I always make in multi-line Makefile commands:
> + LANG=c ; export LANG ; \
> + LC_ALL=c ; export LC_ALL ; \
> @-echo $(INIT_FILES) | \
@ and - are special only on the first command, not if you use
backslashes.
> +# Make certain that the script is running in an internationalized
> +# environment.
Don't you really mean "not" here?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-07-06 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 4:00 Mike Frysinger
2006-07-06 13:32 ` Daniel Jacobowitz [this message]
2006-07-06 18:12 ` Mike Frysinger
2006-07-12 18:04 ` Daniel Jacobowitz
2006-07-13 3:48 ` Mike Frysinger
2006-06-23 0:06 Mike Frysinger
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=20060706133243.GD18827@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.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