uclibc test suite cannot be run because it does not build completely. I think it's important for a libc to have a working test suite. Reproducible: Always Steps to Reproduce: 1. Install Lilblue in December 2013 or January 2014 so you have a uclubc to update 2. FEATURES="test" emerge -1 uclibc Actual Results: emake failed (test phase) Expected Results: uclibc updated on system
Created attachment 380338 [details] emerge --info output
Created attachment 380340 [details] Portage build.log
you've got a custom .config in play. the test links fine w/the default .config.
Created attachment 382188 [details] uclibc savedcondig Here is the savedconfig I use, basically the one blueness used to make Lilblue in late 2013.
(In reply to René Rhéaume from comment #4) > Created attachment 382188 [details] > uclibc savedcondig > > Here is the savedconfig I use, basically the one blueness used to make > Lilblue in late 2013. I've been recently working with test on uclibc and there are quite a few other issues. This is not an illigitimate bug, but its probably buried under lots of other buggy cruft.
I listed the symbols inside the library and though y0, y1 and yn are present, neither their single-precision (y0f, y1f and *ynf*) nor their extended-precision (y0l, y1l and ynl) versions are there. The following comes from the corresponding manual pages from the Linux man-pages project: The functions returning double conform to SVr4, 4.3BSD, POSIX.1-2001. The others are nonstandard functions that also exist on the BSDs. Standards and size considerations might be the reason why uclibc does not include these functions, so tests for ynf() can be skipped if there are equivalent tests for yn().
sys-libs/uclibc has been removed from the tree, replaced by sys-libs/uclibc-ng. if this is still a problem on uclibc-ng, please open a new bug.
