This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug build/19813] New: Failure when cross-testing using cross-test-ssh.sh
- From: "martin.galvan at tallertechnologies dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Fri, 11 Mar 2016 21:37:28 +0000
- Subject: [Bug build/19813] New: Failure when cross-testing using cross-test-ssh.sh
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=19813
Bug ID: 19813
Summary: Failure when cross-testing using cross-test-ssh.sh
Product: glibc
Version: 2.24
Status: NEW
Severity: critical
Priority: P2
Component: build
Assignee: unassigned at sourceware dot org
Reporter: martin.galvan at tallertechnologies dot com
CC: carlos at redhat dot com
Target Milestone: ---
This was previously reported here:
https://sourceware.org/ml/libc-alpha/2016-02/msg00270.html
I'm trying to run the glibc test suite on a cross-compiled environment. The
glibc host is a Beaglebone Black running Debian, and I'm using
cross-test-ssh.sh to connect to it.
Here's what I'm running:
make test-wrapper='/home/martin/glibc/scripts/cross-test-ssh.sh
debian@192.168.5.117' tests
And this is what I'm getting:
touch: cannot touch â/home/martin/glibc/build/localedata/de_DE.UTF-8/LC_CTYPEâ:
No such file or directory
/bin/sh: 4: cannot create
/home/martin/glibc/build/localedata/de_DE.UTF-8/LC_CTYPE.test-result: Directory
nonexistent
make[2]: *** [/home/martin/glibc/build/localedata/de_DE.UTF-8/LC_CTYPE] Error 2
make[2]: Leaving directory `/home/martin/glibc/source/localedata'
make[1]: *** [localedata/tests] Error 2
make[1]: Leaving directory `/home/martin/glibc/source'
make: *** [tests] Error 2
Notice I correctly mirrored my machine's file system into the Beaglebone's.
Just in case, here's my configure line:
$ ../source/configure --prefix=/home/martin/glibc/install/
CC=arm-linux-gnueabihf-gcc --target=arm-linux-gnueabihf
--host=arm-linux-gnueabihf
--build=$(/home/martin/glibc/source/scripts/config.guess)
It's certainly NOT a configure issue, as I was able to run the tests without
specifying a test-wrapper (many tests were UNRESOLVED, as expected). I was also
able to correctly run all the tests in my machine using a native glibc build.
--
You are receiving this mail because:
You are on the CC list for the bug.