This is the mail archive of the
mailing list for the glibc project.
Re: Cross testing error question
- From: "H.J. Lu" <hjl dot tools at gmail dot com>
- To: Steve Ellcey <sellcey at imgtec dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Mon, 8 Feb 2016 14:51:31 -0800
- Subject: Re: Cross testing error question
- Authentication-results: sourceware.org; auth=none
- References: <f37aa381-a8ac-456a-922c-ea890f3f5cac at BAMAIL02 dot ba dot imgtec dot org>
On Mon, Feb 8, 2016 at 2:20 PM, Steve Ellcey <firstname.lastname@example.org> wrote:
> I have a glibc cross-testing question. I was able to do some testing last
> week using the cross-test-ssh.sh script but after rebuilding glibc and
> running the tests again I got a couple of process errors that caused the make
> to stop. I think the reason I was able to test last week was that I did an
> initial 'make check' with -k and then retested after that. The -k option on
> the first run got me through errors like this:
> Generating locale de_DE.ISO-8859-1: this might take a while...
> touch: cannot touch `/home/sellcey/gcc/gcc_cross_testing/obj-mips-mti-linux-gnu/glibc/obj_default/localedata/de_DE.ISO-8859-1/LC_CTYPE': No such file or directory
> /bin/sh: line 3: /home/sellcey/gcc/gcc_cross_testing/obj-mips-mti-linux-gnu/glibc/obj_default/localedata/de_DE.ISO-8859-1/LC_CTYPE.test-result: No such file or directory
> make: *** [/home/sellcey/gcc/gcc_cross_testing/obj-mips-mti-linux-gnu/glibc/obj_default/localedata/de_DE.ISO-8859-1/LC_CTYPE] Error 1
> make: Leaving directory `/home/sellcey/gcc/gcc_cross_testing/src/glibc/localedata'
> make: *** [localedata/tests] Error 2
> make: Leaving directory `/home/sellcey/gcc/gcc_cross_testing/src/glibc'
> If I run 'make check' (without -k) I get this error and then the next time,
> instead of complaining about de_DE.ISO-8859-1, it complains about de_DE.UTF-8,
> then en_US.ANSI_X3.4-1968. I.e. it seems to proceed forward by one language
> at a time if I do not use -k. If I build with -k, it gets through all of these
> but with errors and my understanding was that -k should not be needed when
> testing glibc anymore.
> Has anyone else seen these errors when testing glibc?
> Steve Ellcey
Did you run into