Summary: | sys-libs/glibc-2.12.2: building glibc interrupted in OpenVZ container, also tried rebuilding system | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Thomas Urban <soletan> |
Component: | [OLD] Unspecified | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | andreis.vinogradovs, pva |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log and environment from /var/tmp/... |
Description
Thomas Urban
2011-06-28 08:35:29 UTC
Please, attache logs in English locale to bugzilla (it's good idea to avoid storing relevant information outside bugzilla if possible). Are you talking about glibc in container or on server? Does all containers expose same problem? Hi, currently it's just a single Gentoo-based container on CentOS-based server running OpenVZ environment. I decided to use different distro on all further containers since this one is consuming too much resources on frequent updates. But it's still running some essential applications. On building glibc with updated locale I realized some early failures on making something in preparation for building it. Maybe that's part of the problem ... Find attached updated build log and environment. Created attachment 278691 [details]
build.log and environment from /var/tmp/...
Looks like you have problems with your gcc, have you tried rebuilding it? :-/ Rebuilt a fresh gcc 4.4.5, but compiling glibc still fails. I remember having tried switching to the two older versions of gcc using gcc-config before. That's annoying ... since the server is kept blocked it might be good to have a different distro. Does rebuild fails in the same place all the time? Try to rebuild toolchain, sandbox and bash as well. Also... this looks related to bug 348640 so try to update sandbox to 2.5. (In reply to comment #6) > Does rebuild fails in the same place all the time? Try to rebuild toolchain, > sandbox and bash as well. Also... this looks related to bug 348640 so try to > update sandbox to 2.5. Tried rebuilding sandbox (2.4) and bash. "toolchain" is not a package name as known by emerge, is it? What do you mean exactly? emerging "system" ... tried that before. upgrading to sandbox 2.5 is currently no option due to being masked by amd64. And it's a production server, so I can't test. And yes, according to my last trials it's always failing at the same point: --- CPP='x86_64-pc-linux-gnu-gcc -m64 -E -x c-header' /var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/elf/ld-linux-x86-64.so.2 --library-path /var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl:/var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/math:/var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/elf:/var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/dlfcn:/var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/nss:/var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/nis:/var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/rt:/var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/resolv:/var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/crypt:/var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/nptl /var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/sunrpc/rpcgen -Y ../scripts -h rpcsvc/nlm_prot.x -o /var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/sunrpc/rpcsvc/nlm_prot.T /usr/lib64/libsandbox.so(+0x3932)[0x2ac076c02932] /usr/lib64/libsandbox.so(+0x39c3)[0x2ac076c029c3] /usr/lib64/libsandbox.so(+0x5a9f)[0x2ac076c04a9f] /usr/lib64/libsandbox.so(+0x616a)[0x2ac076c0516a] /usr/lib64/libsandbox.so(+0x6f75)[0x2ac076c05f75] /usr/lib64/libsandbox.so(execve+0x63)[0x2ac076c07993] /bin/sh(shell_execve+0x43)[0x2ac076719333] /bin/sh(+0x482b8)[0x2ac07671f2b8] /bin/sh(execute_command_internal+0xafd)[0x2ac07671b85d] /bin/sh(parse_and_execute+0x20a)[0x2ac076762b8a] /proc/20319/cmdline: /var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/elf/ld-linux-x86-64.so.2 --library-path /var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl:/var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/math:/var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/elf:/var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/dlfcn:/var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/nss:/var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/nis:/var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/rt:/var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/resolv:/var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/crypt:/var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/nptl /var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/sunrpc/rpcgen -Y ../scripts -c rpcsvc/nlm_prot.x -o /var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/sunrpc/xnlm_prot.T /bin/sh ../scripts/move-if-change /var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/sunrpc/xbootparam_prot.T /var/tmp/portage/sys-libs/glibc-2.12.2/work/build-amd64-x86_64-pc-linux-gnu-nptl/sunrpc/xbootparam_prot.c (In reply to comment #7) > Tried rebuilding sandbox (2.4) and bash. "toolchain" is not a package name as > known by emerge, is it? What do you mean exactly? emerging "system" ... Toolchain is a synonym to the packages needed to build other packages (most commonly gcc, glibc, binutils, but may also be extended to coreutils, and other system-essential packages). "emerge -e system" usually catch all these. (In reply to comment #8) > (In reply to comment #7) > > Tried rebuilding sandbox (2.4) and bash. "toolchain" is not a package name as > > known by emerge, is it? What do you mean exactly? emerging "system" ... > > Toolchain is a synonym to the packages needed to build other packages (most > commonly gcc, glibc, binutils, but may also be extended to coreutils, and other > system-essential packages). "emerge -e system" usually catch all these. Thanks for clarification. Though I'm familiar with toolchains including make, autoconfig, gcc etc. I was just asking to exclude having overseen something. As mentioned in my initial post, I also tried emerge -eav system ... I tried different gcc version, have rebuild gcc ... and failcnt in /proc/user_beancounter are all 0 thus excluding OOM conditions. And sandbox-2.5 is stable now. Please, retest with updated sandbox. Did emerge --sync, then emerge portage, then emerge sandbox ... all succeeding. Had to fix several packages causing longer list on outdated __guard found and required to be removed prior to emerging world. Finally got rid of that, then emerged world with glibc in very first position. But it keeps on breaking at selected position. Tried emerging system with -eav, but it's trying to emerge glibc first, so is failing as well. pva: may be this bug is outdated ? ( el5 branch kernel, old glibc .. ) Can not reproduce with up-to-date kernel and glibc. Feel free to reopen if it is still an issue |