On 2007-04-21, Steve Langasek <[EMAIL PROTECTED]> wrote: > On Sat, Apr 21, 2007 at 07:41:00PM +0200, Adeodato Simó wrote: >> d-r: > >> ruby1.8_1.8.6-1, rebuild against latest libc6-dev to drop eaccess from >> missing.h, 1, alpha amd64 arm hppa i386 ia64 m68k mips mipsel powerpc s390 >> sparc > > Scheduled, with dep-wait set on libc6-dev 2.5 as I assume that's the version > providing the eaccess prototype.
Short version: The dep-wait didn't work for mips and mipsel for some reason, so can you binNMU ruby1.8 on mips and mipsel again? Long version: The binNMU doesn't seem to have used the right libc6-dev version on mips or mipsel. For mips: http://buildd.debian.org/fetch.cgi?pkg=ruby1.8;ver=1.8.6-1%2Bb1;arch=mips;stamp=1177496689 Toolchain package versions: libc6-dev_2.3.6.ds1-9 linux-kernel-headers_2.6.18-6 gcc-4.1_4.1.1-21 g++-4.1_4.1.1-21 binutils_2.17-3 libstdc++6-4.1-dev_4.1.1-21 libstdc++6_4.1.1-21 And for mipsel: http://buildd.debian.org/fetch.cgi?pkg=ruby1.8;ver=1.8.6-1%2Bb1;arch=mipsel;stamp=1177755123 Toolchain package versions: libc6-dev_2.3.6.ds1-13 linux-kernel-headers_2.6.18-7 gcc-4.1_4.1.1-21 g++-4.1_4.1.1-21 binutils_2.17-3 libstdc++6-4.1-dev_4.1.1-21 libstdc++6_4.1.1-21 So the problem with the ruby1.8-dev headers which caused bug #420325 still exists for mips and mipsel, and has caused xapian-bindings to fail to build in the same way as in the original bug report: http://buildd.debian.org/fetch.cgi?pkg=xapian-bindings;ver=1.0.1-1;arch=mips;stamp=1181832758 /usr/include/unistd.h:270: error: declaration of 'int eaccess(const char*, int) throw ()' throws different exceptions /usr/lib/ruby/1.8/mips-linux/missing.h:43: error: from previous declaration 'int eaccess(const char*, int)' (and the same error for mipsel). The build logs for xapian-bindings I link to above show: Toolchain package versions: libc6-dev_2.5-7 linux-kernel-headers_2.6.18-7 gcc-4.1_4.1.2-12 g++-4.1_4.1.2-12 binutils_2.17cvs20070426-6 libstdc++6-4.1-dev_4.1.2-12 libstdc++6_4.2-20070528-1 (and those for mipsel show the same version), so a binNMU now should fix this problem. Cheers, Olly -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
