diff options
author | Thomas Schwinge <thomas@codesourcery.com> | 2013-01-08 21:34:29 +0100 |
---|---|---|
committer | Thomas Schwinge <thomas@codesourcery.com> | 2013-01-08 21:43:11 +0100 |
commit | cd42b6144bf707fa38555bc06e267bb16db011f5 (patch) | |
tree | ddebd4ae1c845bd062261b4335a9ab7a969a3c89 /open_issues/glibc.mdwn | |
parent | a91114fc89dd554494801349e57bd5d29454a8b1 (diff) | |
parent | e66cb01b99b60f9483de2425bca3bb104bcc9ae8 (diff) | |
download | web-cd42b6144bf707fa38555bc06e267bb16db011f5.tar.gz web-cd42b6144bf707fa38555bc06e267bb16db011f5.tar.bz2 web-cd42b6144bf707fa38555bc06e267bb16db011f5.zip |
Merge remote-tracking branch 'fp/master'
Diffstat (limited to 'open_issues/glibc.mdwn')
-rw-r--r-- | open_issues/glibc.mdwn | 15 |
1 files changed, 12 insertions, 3 deletions
diff --git a/open_issues/glibc.mdwn b/open_issues/glibc.mdwn index 26e04768..4111700b 100644 --- a/open_issues/glibc.mdwn +++ b/open_issues/glibc.mdwn @@ -1180,9 +1180,6 @@ There is quite a baseline of failures. * `tst-array*` - Failures also seen on GNU/Linux; [[!message-id - "50950082.1070906@df1tl.local.here"]]. - gcc-4.6 tst-array1.c -c -std=gnu99 -fgnu89-inline -O2 -Wall -Winline -Wwrite-strings -fmerge-all-constants -frounding-math -g -Wno-parentheses -Wstrict-prototypes -I../include -I[...]/tschwinge/Roger_Whittaker.build-gcc-4.6-486/ gcc-4.6 -nostdlib -nostartfiles -o [...]/tschwinge/Roger_Whittaker.build-gcc-4.6-486/elf/tst-array1 -Wl,-dynamic-linker=/lib/ld.so.1 -Wl,-z,combreloc -Wl,-z,relro -Wl,--hash-style=both [...]/tschwinge/Roger_Whittaker.build-gcc-4.6-486 [...]/tschwinge/Roger_Whittaker.build-gcc-4.6-486/elf/ld.so.1 --library-path [...]/tschwinge/Roger_Whittaker.build-gcc-4.6-486:[...]/tschwinge/Roger_Whittaker.build-gcc-4.6-486/math:[...]/tschwinge/Roger_Whittaker.build-gcc-4.6-486/elf:[ @@ -1216,6 +1213,18 @@ There is quite a baseline of failures. `tst-array5-static` passes. + IRC, freenode, #glibc, 2012-11-01: + + <jsm28> tschwinge: I saw the array tests fail, built a new binutils and + a new compiler configured with new binutils and the failures went + away. + <jsm28> So they may depend on having new-enough GCC configured with + new-enough binutils, or something like that. + <tuliom> jsm28: Did you use gcc 4.7 or trunk? + <jsm28> tuliom: 4.7. + + [[!message-id "50950082.1070906@df1tl.local.here"]]. + * `tst-audit1.out`, `tst-audit2.out` SIGKILL. |