This is the mail archive of the
mailing list for the glibc project.
Re: Include LOCPATH in default test environment
- From: Florian Weimer <fweimer at redhat dot com>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Wed, 11 Jun 2014 13:12:07 +0200
- Subject: Re: Include LOCPATH in default test environment
- Authentication-results: sourceware.org; auth=none
- References: <Pine dot LNX dot 4 dot 64 dot 1406042243420 dot 2874 at digraph dot polyomino dot org dot uk> <53980F34 dot 2070300 at redhat dot com> <Pine dot LNX dot 4 dot 64 dot 1406111021090 dot 17228 at digraph dot polyomino dot org dot uk>
On 06/11/2014 12:24 PM, Joseph S. Myers wrote:
On Wed, 11 Jun 2014, Florian Weimer wrote:
On 06/05/2014 12:44 AM, Joseph S. Myers wrote:
Tests run using the default $(make-test-out) automatically get
GCONV_PATH and LC_ALL set, whether or not those environment variables
are actually needed for the individual test. However, they do not get
LOCPATH set, meaning that a large number of tests have -ENV settings
just to set LOCPATH.
Is it still necessary to ensure manually that the localedata subdirectory is
built in time, before tests relying on LOCPATH run?
If a directory contains tests using locales, my understanding is that its
Depend file should mention localedata to ensure that localedata comes
first in sysd-sorted.
I don't think this is possible for locale/ because that would introduce
a cyclic dependency.
What I'm trying to say is that it might make sense to artificially
introduce a barrier between building localedata/ and running the tests,
if that's possible, so that it's no longer necessary to touch the Depend
Florian Weimer / Red Hat Product Security Team