Yaboot 1.3.17 released.

[acrux]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 19 Oct 2011 09:19:34 +1100
Tony Breeds <tony at bakeyournoodle.com> wrote:

_omissis__
> + patch -p0 -i /mnt/DEVEL/next/yaboot/work/src/chrpfix.patch
> + patch -p0
> 
> Are either of these 2 patches things that I should consider for
> upstream?
> 

it's a patch i got from gentoo.
http://cruxppc.org/viewvc/opt/branches/2.7/yaboot/chrpfix.patch?revision=1989&view=markup
It applies util/addnote to make available a new yaboot.chrp. Actually i don't have an old IBM Chrp32 to test it.
Anyway i use to dd this yaboot.chrp in my PReP Boot partition on our pseries (POWER4+ and POWER5) and our YDL Powerstation. It works but i guess that it really affect only old rs6k 32bit machines.


> second/fs_swap.c:90:15: warning: unused variable
> 'rc' [-Wunused-variable] second/fs_reiserfs.c:221:17: warning:
> operation on '*journal_table' may be undefined [-Wsequence-point]
> second/fs_reiserfs.c:221:17: warning: operation on '*journal_table'
> may be undefined [-Wsequence-point] second/fs_reiserfs.c:221:17:
> warning: operation on '*journal_table' may be undefined
> [-Wsequence-point] second/fs_reiserfs.c:224:12: warning: operation on
> 'journal_table' may be undefined [-Wsequence-point]
> second/fs_reiserfs.c:224:12: warning: operation on 'journal_table'
> may be undefined [-Wsequence-point] second/fs_reiserfs.c:224:12:
> warning: operation on 'journal_table' may be undefined
> [-Wsequence-point] second/fs_reiserfs.c:243:12: warning: operation on
> 'i' may be undefined [-Wsequence-point] second/fs_reiserfs.c:243:12:
> warning: operation on 'i' may be undefined [-Wsequence-point]
> second/fs_reiserfs.c:243:12: warning: operation on 'i' may be
> undefined [-Wsequence-point] second/fs_reiserfs.c:255:10: warning:
> operation on 'i' may be undefined [-Wsequence-point]
> second/fs_reiserfs.c:255:10: warning: operation on 'i' may be
> undefined [-Wsequence-point] second/fs_reiserfs.c:255:10: warning:
> operation on 'i' may be undefined [-Wsequence-point]
> ---
> 
> I've not seen those warnings before, what version of gcc are you
> using? The ones in fs_reiserfs.c are frsutrating as I thought I'd
> fixed that function in .17
> 

It's gcc-4.5.3, here the output version from my CRUX PPC 2.7 (32bit):

[96%][H] acrux at hermes:~$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/powerpc-unknown-linux-gnu/4.5.3/lto-wrapper
Target: powerpc-unknown-linux-gnu
Configured with: ../gcc-4.5.3/configure --disable-multilib --prefix=/usr --mandir=/usr/man --libexecdir=/usr/lib --enable-languages=c,c++,objc --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-shared --disable-nls --with-x=no --enable-long-long --with-system-zlib --with-pkgversion='CRUX PPC' --host=powerpc-unknown-linux-gnu --build=powerpc-unknown-linux-gnu --target=powerpc-unknown-linux-gnu
Thread model: posix
gcc version 4.5.3 (CRUX PPC) 


cheers,
- --nico
- -- 
GNU/Linux on Power Architecture
CRUX PPC - http://cruxppc.org/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iEYEARECAAYFAk6fNcUACgkQxq34tDeO7LglAwCeKRLJ98pAvZckqhqtMFtyCjNU
KmAAniVFCieLSJ8YmMLLn/ejhQCmbaia
=FONf
-----END PGP SIGNATURE-----