On uclibc systems, a few cases for the t-scanf test are GLIBC-specific. However, the __GLIBC__ token is also defined on uclibc and will make tests failres on that platform. Reproducible: Always Steps to Reproduce: 1. FEATURES="test" emerge -1 gmp 2. 3. Actual Results: emake failed (test phase) Expected Results: gmp updated on system
Created attachment 414248 [details, diff] gmp-6.0.0a-uclibc-tests.diff No ebuild patch is needed if you put this source code patch into ${FILESDIR}/6.0.0a
Please include emerge --info and the failing build log too.
Created attachment 414350 [details] build.log from emerge
Created attachment 414352 [details] emerge --info output
Rene, I wasn't able to hit this with uclibc-0.9.33.2-r15. you're using -r4. i know there have been upstream uclibc commits to fix some scanf stuff. i'll take a look. you can upgrade uclibc on your system, just be careful that it uses the same config file. -r4 is a bit old now and has some bugs that will affect e2fsprogs.
Rene, can you try test the following program. See if it fails any assertions. #include <stdio.h> #include <assert.h> int main() { char buf[128]; int n = -1; int ret, cmp; buf[0] = '\0'; ret = sscanf ("abcdefgh", "%[a-d]ef%n", buf, &n); assert (ret == 1); cmp = strcmp (buf, "abcd"); assert (cmp == 0); assert (n == 6); ret = sscanf ("xyza", "%[^a]a%n", buf, &n); assert (ret == 1); cmp = strcmp (buf, "xyz"); assert (cmp == 0); assert (n == 4); ret = sscanf ("ab]ab]", "%[]ab]%n", buf, &n); assert (ret == 1); cmp = strcmp (buf, "ab]ab]"); assert (cmp == 0); assert (n == 6); ret = sscanf ("xyzb", "%[^]ab]b%n", buf, &n); assert (ret == 1); cmp = strcmp (buf, "xyz"); assert (cmp == 0); assert (n == 4); }
(In reply to Anthony Basile from comment #6) > Rene, can you try test the following program. See if it fails any > assertions. > With uclibc-0.9.33.2-r4, I get this on standard error: ./test-scanf: test-scanf.c: 14: main: Assertion `cmp == 0' failed. With uclibc-0.9.33.2-r15, this error does not happen.
Also, on uclibc-0.9.33.2-r15, test suite succeeds without patching.
(In reply to René Rhéaume from comment #8) > Also, on uclibc-0.9.33.2-r15, test suite succeeds without patching. yep this was fixed and mike backported the patch.