| Summary: | sys-devel/glibc-2.10.1 fails to build when /bin/sh is pointing to zsh | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Ivan Kouvykov <ivan.kouvykov> |
| Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | axiator |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
tail -n 300 /var/tmp/portage/sys-libs/glibc-2.10.1/temp/build.log
build.log |
||
|
Description
Ivan Kouvykov
2009-05-27 12:10:41 UTC
Created attachment 192583 [details]
tail -n 300 /var/tmp/portage/sys-libs/glibc-2.10.1/temp/build.log
post the full build log are you using a hardened toolchain or otherwise screwing around with gcc ? (In reply to comment #2) > post the full build log > > are you using a hardened toolchain or otherwise screwing around with gcc ? > No, I don't use hardened. I'm using the latest gcc from ~amd64 with default use flags. sys-devel/gcc-4.3.3-r2(4.3)!s(01:40:41 AM 04/23/2009)(doc fortran mudflap multilib nls openmp -altivec -bootstrap -build -fixed-point -gcj -gtk -hardened -ip28 -ip32r10k -libffi -multislot -n32 -n64 -nocxx -nopie -objc -objc++ -objc-gc -test -vanilla) How do I post the whole build.log? (It's about 7MB large) you are familiar with compression utilities, right ? Created attachment 192680 [details]
build.log
Bug resolved by fixing /bin/sh symlink (it was pointing to /bin/zsh instead of /bin/bash) afaik, zsh is not POSIX compliant, and it certainly isnt supported as a /bin/sh replacement |