Impending doom of my linux-ppc buildbot

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 By the end of the summer I'll have stopped having access to a powerpc system (although qemu could emulate any architecture system...), and hopefully I'll have stopped using it much sooner. Before leaving this I thought it would be nice to clear something up: Does anyone remember why there is this following allegation of a special case for threading support? Is it still applicable, or can we get rid of it: " In addition to the above commands Yhc can also be built with the follow options. [...] threads=0 (default=1, except on ppc where the default is 0) Disables threading. [...] " Isaac -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGhEAfHgcxvIWYTTURAislAJ9z46yXI4X5458xFUOMFgkkBoRdwgCfaoxd TpvFXw15u8CGQk0wXEJq/tg= =thBU -----END PGP SIGNATURE-----

Isaac Dupree wrote:
By the end of the summer I'll have stopped having access to a powerpc system (although qemu could emulate any architecture system...), and hopefully I'll have stopped using it much sooner.
Well, my linux-ppc buildbot is gone now. Probably never will run again. Isaac

Hi Isaac,
Well, my linux-ppc buildbot is gone now. Probably never will run again.
We'll miss it :-) It caught a bug that on Linux PPC char is unsigned by default, something we'd have never found without it. As a related note, if anyone has some alternative hardware for a Yhc buildbot, let us know. Something SPARC/Sun related would be nice, if its lying around. Thanks Neil
participants (2)
-
Isaac Dupree
-
Neil Mitchell