Summary: | sys-libs/glibc-2.20-r2 recompilation issue | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dmitri Seletski <drjoms> |
Component: | [OLD] Library | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge --info '=sys-libs/glibc-2.20-r2::gentoo'
glibc-2.20-r2/temp/build.log environment file. |
Created attachment 414292 [details]
glibc-2.20-r2/temp/build.log
500 lines of text (log is 10 megs) from bottom of log file.
Created attachment 414294 [details]
environment file.
/mnt/dump/portage/portage/sys-libs/glibc-2.20-r2/temp/environment
I changed path, because i have small root hdd(60 gb ssd). At time of compilation I unmounted the portage partition to avoid any problems.
one of reasons i am trying to recompile glibc: checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... configure: error: in `/mnt/dump/portage/portage/dev-libs/expat-2.1.0-r5/work/expat-2.1.0-abi_x86_32.x86': configure: error: cannot run C compiled programs. If you meant to cross compile, use `--host'. See `config.log' for more details trying to compile dev-libs/expat-2.1.0-r5 for skype. I can reproduce this. USE=gd seems to trigger it. I have attempted to build masked packages of glibc, same story. since I have FEATURES=fail-clean I used USE=gd MAKEOPTS=-j1 ebuild /usr/portage/sys-libs/glibc/glibc-2.20-r2.ebuild compile to investigate. Not getting any errors, install and merge also worked. Strangely enough, now a normal emerge also does not produce errors anymore. I have replaced non working gcc and glibc. I suppose bug can be closed, unless someone can reproduce it. |
Created attachment 414290 [details] emerge --info '=sys-libs/glibc-2.20-r2::gentoo' a little bit about background: I emerged world -D recently(couple of days ago). I unmerged all non amd64 packages. I have no emulation of any kind. I moved to systemd. My kernel supports 32 bit. I had steam(no overlays, binary file in home directory) complaining that my libc does not support 32 bit. I made health check on glibc. It showed some problems. Naturally I decided re-emerge it. and I encountered said problem. I want to install a few programs/libraries so I can run steam/skype I don't want to make my whole system "multilib". I don't mind modifying /etc/portage/package.use for that. But right now I guess biggest problem is glibc. is this normal to reinstall glibc? Please see other files attached. [ebuild R ] sys-libs/glibc-2.20-r2 USE="gd (multilib) -debug (-hardened) -nscd -profile (-selinux) -suid -systemtap -vanilla" * Working directory: '/mnt/dump/portage/portage/sys-libs/glibc-2.20-r2/work/glibc-2.20' * S: '/mnt/dump/portage/portage/sys-libs/glibc-2.20-r2/work/glibc-2.20'