User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.7) Gecko/20060925 Epiphany/2.14 Firefox/1.5.0.7 Build Identifier: Request that colo-1.22 be added to portage. Portage will build colo-1.22 if Redhatter's colo-1.21.ebuild has been copied/renamed to "colo-1.22.ebuild". Tested for clean build on Cobalt RaQ2 w/ gcc-3.4.6 and Cobalt NASRaQ w/ gcc-4.1.1. I am currently testing for functionality, but seems OK so far. Reproducible: Always Steps to Reproduce: 1. ACCEPT_KEYWORDS="~mips" emerge -av colo Actual Results: Calculating dependencies... done! [ebuild U ] sys-boot/colo-1.21 [1.19] 249 kB Expected Results: Calculating dependencies... done! [ebuild U ] sys-boot/colo-1.22 [1.19] 2?? kB I'll attach minimally modified version of Redhatter's ebuild when I get a chance, but it looks like only the name needs changing. I can attach the relevant 'emerge --info' for both systems, but are they really desired for such a straight foreward ehancement request?
Created attachment 98795 [details] colo-1.22.ebuild Renamed version of Redhatter's colo-1.21.ebuild
I just figured out that the current stable version (1.19) does not compile any more: [...] gcc -Werror -Wall -Wstrict-prototypes -fomit-frame-pointer -O2 -fno-strict-aliasing -march=r5000 -ffreestanding -mno-abicalls -fno-PIC -G0 -nostdinc -Iinclude -I../include -D_DEBUG -I/usr/lib/gcc/mipsel-unknown-linux-gnu/4.1.1/include -c -o nfs.o src/nfs.c cc1: warnings being treated as errors src/nfs.c: In function 'nfs_read_dir': src/nfs.c:607: warning: pointer targets in passing argument 2 of 'func' differ in signedness src/nfs.c: In function 'dump_node': src/nfs.c:738: warning: pointer targets in passing argument 2 of 'nfs_readlink' differ in signedness make[1]: *** [nfs.o] Error 1 make[1]: Leaving directory `/var/tmp/portage/colo-1.19/work/colo-1.19/stage2' make: *** [subdirs] Error 2 mips team: plase add 1.22 to portage or give the ok and I'll do so.
Yeah, in the business of the latter part of 2006, I actually missed this bug. I plan to commit CoLo 1.22 straight to stable -- since the earlier versions do not compile against GCC 4.1. This shouldn't cause any breakage of machines, however, it'd be wise to keep your vmlinux.gz file backed up just-in-case. If things do go west, hold down the password-reset button whilst turning the unit on until "Console ON" appears, then power-cycle the box. At the serial console ... hit space quickly, and at the prompt, execute: > bfd vmlinux.gz.old (I think that's the command... long time since I last did this) For the record, it was a drop-in replacement here.
colo 1.22 is in the tree since a few weeks. marking bug as FIXED
