Just an update on where I am with ppc64. Progress in building is
slow (my G5 is comparatively slow, and I'm not able to run it as
much as I'd like because of the heat in the room).
1. The 32-bit glibc tests are as bad as ever - I assume the 'catgets'
failures are what the book describes as "gettext" ? There are a lot
of other errors which look pretty nasty, but they've been there for
as long as I can remember (since November, when I first tried ppc64),
and pretty much the same thing happened to me on x86_64 multilib
when I last tried that. Anybody got a link for 32-bit glibc test
results on x86_64 ?
2. I've finally got around around to looking at the binutils test
failures (again, they've always been there, 18 failures in ld
visibility). Looking at ld/testsuite/ld-elfvsb/elfvsb.exp I'm
totally confused - it starts
# This test can only be run on a couple of ELF platforms.
# Square bracket expressions seem to confuse istarget.
if { ![istarget hppa*64*-*-hpux*] \
&& ![istarget hppa*-*-linux*] \
&& ![istarget i?86-*-linux*] \
&& ![istarget ia64-*-linux*] \
&& ![istarget m68k-*-linux*] \
&& ![istarget mips*-*-linux*] \
&& ![istarget powerpc*-*-linux*] \
&& ![istarget arm*-*-linux*] \
&& ![istarget alpha*-*-linux*] \
&& ![istarget sparc*-*-linux*] \
&& ![istarget s390*-*-linux*] \
&& ![istarget sh\[34\]*-*-linux*] \
&& ![istarget x86_64-*-linux*] } {
return
}
if { [istarget *-*-linux*aout*] \
|| [istarget *-*-linux*oldld*] } {
return
}
but then a little later there is
if { [istarget rs6000*-*-aix*] || [istarget powerpc*-*-aix*] } {
- how would either of these get past the first test ?
Does anybody here understand 'expect', and if so can they please
supply me with pointers to debugging this script, even simple things
like how to get it to print variables, or to print that a test is
passed, would be useful to me.
TIA
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
_______________________________________________
Clfs-dev mailing list
[email protected]
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev