Summary: | sys-devel/binutils-2.22[cxx,test]: gold test fails when sys-libs/zlib[-static-libs] | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | nikoli |
Priority: | Normal | Keywords: | TESTFAILURE |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build log
compressed build.log |
Description
Toralf Förster
2011-12-21 08:41:10 UTC
Created attachment 296535 [details]
build log
pretty sure not a regression Created attachment 324246 [details]
compressed build.log
Same here in a chrooted environtment with the same version:
=== ld Summary ===
# of expected passes 604
# of unexpected failures 44
# of expected failures 8
# of untested testcases 1
/var/tmp/portage/sys-devel/binutils-2.22-r1/work/build/ld/ld-new 2.22
make[5]: *** [check-DEJAGNU] Error 1
make[5]: Leaving directory `/var/tmp/portage/sys-devel/binutils-2.22-r1/work/build/ld'
make[4]: *** [check-am] Error 2
make[4]: Leaving directory `/var/tmp/portage/sys-devel/binutils-2.22-r1/work/build/ld'
make[3]: *** [check-recursive] Error 1
make[3]: Leaving directory `/var/tmp/portage/sys-devel/binutils-2.22-r1/work/build/ld'
make[2]: *** [check] Error 2
make[2]: Leaving directory `/var/tmp/portage/sys-devel/binutils-2.22-r1/work/build/ld'
make[1]: *** [check-ld] Error 2
make[1]: Target `check-host' not remade because of errors.
make[1]: Leaving directory `/var/tmp/portage/sys-devel/binutils-2.22-r1/work/build'
make: *** [do-check] Error 2
make: Target `check' not remade because of errors.
emake failed
chrooting was done via:
mount -t proc none /mnt/tmp/proc
mount --rbind /sys /mnt/tmp/sys
mount --rbind /dev /mnt/tmp/dev
chroot /mnt/tmp /bin/bash
and after chrooting:
env-update && source /etc/profile
Some other packages like dbus also fail on some tests.
Perhaps there is some relation on that.
(In reply to comment #3) > and after chrooting: > > env-update && source /etc/profile OT - nevertheless I think this isn't necessary if you do "su -", eg. this is what I was doing till today - except mounting /sys, this was stolen today from your method :) ... mount -o loop $ROOT_FS $MNT mount -t proc none $MNT/proc mount -o bind /dev $MNT/dev mount -o bind /dev/pts $MNT/dev/pts mount -o bind /sys $MNT/sys mount -o bind /usr/portage $MNT/usr/portage mount -o bind /usr/local/portage $MNT/usr/local/portage mount -o bind $TMPPORTAGE $MNT/var/tmp/portage chroot $MNT /bin/bash -c "su -" RC=$? umount $MNT/var/tmp/portage umount $MNT/usr/local/portage umount $MNT/usr/portage umount $MNT/sys umount $MNT/dev/pts umount $MNT/dev umount $MNT/proc umount $MNT pretty sure most of those are unrelated to zlib[static-libs]. are you saying that if you build with zlib[static-libs], all your errors go away ? (In reply to comment #5) Erm - to which comment this is the reply ? (In reply to comment #6) the test failures. i don't care about random user mount issues. this will require updating to EAPI=2 so we can utilize USE depends obsolete |