From: Carlos O'Donell <carlos@redhat.com>
To: Arjun Shankar <arjun.is@lostca.se>, libc-alpha@sourceware.org
Cc: "Gabriel F. T. Gomes" <gabriel@inconstante.net.br>
Subject: Re: [PATCH] Set locale related environment variables in debugglibc.sh
Date: Wed, 23 Sep 2020 21:54:46 -0400 [thread overview]
Message-ID: <c68f5686-a5cc-cea7-b942-d1265079ff3f@redhat.com> (raw)
In-Reply-To: <20200923160655.GA16688@aloka.lostca.se>
On 9/23/20 12:06 PM, Arjun Shankar wrote:
> From: Arjun Shankar <arjun@redhat.com>
>
> Tests and binaries that use locale related functions need to run in the
> correct locale environment when being debugged via debugglibc.sh. This
> commit sets up the environment, specifically: GCONV_PATH, LOCPATH, and
> LC_ALL for such tests and binaries when they are being debugged outside
> of a test container.
OK to commit.
Reviewed-by: Carlos O'Donell <carlos@redhat.com>
> ---
> Makefile | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/Makefile b/Makefile
> index 6dcfe40c25..e047e504be 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -305,6 +305,15 @@ then
> exit 1
> fi
>
> +# Container tests needing locale data should install them in-container.
Agreed. And any non-SUPPORTED locales can be built outside of the container
and then installed by the container script. We should try hard to make the
container tests look like normal installs.
> +# Other tests/binaries need to use locale data from the build tree.
> +if [ "$$CONTAINER" == false ]
> +then
> + ENVVARS="GCONV_PATH=$${BUILD_DIR}/iconvdata $$ENVVARS"
OK.
> + ENVVARS="LOCPATH=$${BUILD_DIR}/localedata $$ENVVARS"
OK.
> + ENVVARS="LC_ALL=C $$ENVVARS"
OK.
> +fi
> +
> # Expand environment setup command
> if [ -v ENVVARS ]
> then
>
--
Cheers,
Carlos.
next prev parent reply other threads:[~2020-09-24 1:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 16:06 Arjun Shankar
2020-09-24 1:54 ` Carlos O'Donell [this message]
2020-09-24 7:51 ` Andreas Schwab
2020-09-24 12:55 ` Arjun Shankar
2020-09-25 3:18 ` Carlos O'Donell
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=c68f5686-a5cc-cea7-b942-d1265079ff3f@redhat.com \
--to=carlos@redhat.com \
--cc=arjun.is@lostca.se \
--cc=gabriel@inconstante.net.br \
--cc=libc-alpha@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).