Camm Maguire wrote: |Cc: ..., [EMAIL PROTECTED]
You may have already moticed, there is no such list. mipsel is handled together with mips. > Greetings! The latest gclcvs autobuild succeeds on mipsel with > > Toolchain package versions: libc6-dev_2.3.2.ds1-16 > linux-kernel-headers_2.5.999-test7-bk-17 gcc-3.3_1:3.3.4-11 > g++-3.3_1:3.3.4-11 binutils_2.15-3 libstdc++5_1:3.3.4-11 > libstdc++5-3.3-dev_1:3.3.4-11 > > and fails on mips with > > Toolchain package versions: libc6-dev_2.3.2.ds1-16 > linux-kernel-headers_2.5.999-test7-bk-17 gcc-3.3_1:3.3.4-9 g++-3.3_1:3.3.4-9 > binutils_2.15-3 libstdc++5_1:3.3.4-9 libstdc++5-3.3-dev_1:3.3.4-9 > > > Is this to be expected? If so, are the newer compiler packages going > into mips? If so, can gclcvs be requeued with these? The mips buildlog says: Initializing pcl_gazonk3.o Error: Caught fatal error [memory may be damaged] Error signalled by UPDATE-INITIALIZE-INFO-INTERNAL. Broken at SYSTEM::BREAK-LEVEL. Type :H for Help. PCL>> T >> #<"USER" package> >>rm init_pcl_gcl.lsp raw_pcl_gcl make[2]: Leaving directory `/build/buildd/gclcvs-2.7.0/unixport' (cd clcs; rm -f *.c; /usr/bin/make all) Which may have caused the error. This appears to be some transient buildd error. Thiemo
