On 22/05/12 23:32, Jonathan Nieder wrote:
severity 673596 important
quit
Hi Philip,
Philip Ashmore wrote:
Should I attach /var/log/dmesg?
Unless you've been running into other problems, I wouldn't bother.
I doubt this problem is CPU-specific, though of course I could be
wrong. How reproducible is the test failure? You can run tests again
by removing stamp-dir/check_* and running "debian/rules build" again,
or run a single test explicitly by running
build-tree/i386-i686/elf/ld-linux.so.2 \
--library-path $(pwd)/build-tree/i386-i686:\
$(pwd)/build-tree/i386-i686/math:\
$(pwd)/build-tree/i386-i686/elf:\
$(pwd)/build-tree/i386-i686/dlfcn:\
$(pwd)/build-tree/i386-i686/nss:\
$(pwd)/build-tree/i386-i686/nis:\
$(pwd)/build-tree/i386-i686/rt:\
$(pwd)/build-tree/i386-i686/resolv:\
$(pwd)/build-tree/i386-i686/crypt:\
$(pwd)/build-tree/i386-i686/nptl \
build-tree/i386-i686/nptl/tst-eintr1
(command retrieved with "make -n". The corresponding code is in
Makeconfig.)
Set the LD_TRACE_LOADED_OBJECTS envvar to 1 if you want to make sure
this command is testing the appropriate version of libc. You can also
experiment by checking whether tst-eintr1 works as it should with the
system copy of libc.
I'm lowering the severity because I wasn't able to trigger trouble
building eglibc on this machine (Thinkpad G41, Pentium 4, kernel from
linux-next) so this bug is still missing a reproduction recipe.
Hope that helps,
Jonathan
It looks like you're building on i386 - the bug report is for amd64.
If someone could tell me the steps, I could provide you with the automated
install script
to set up Debian Wheezy in VMware so it's the same as mine, allowing others to
reproduce the problem.
Philip
--
To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4fbcfb39.2030...@philipashmore.com
