I just wanted to build my first hardened AMD64 system and ran into the
following problem after chrooting into the unpacked tarball:
(2007-0 AMD64 multilib - keywords: amd64)
$ emerge --sync
[..]
$ ls -l /etc/make.profile
lrwxrwxrwx 1 root root 47 Dec 14
00:34 /etc/make.profile -> ../usr/portage/profiles/hardened/amd64/multilib
$ emerge -p binutils gcc glibc
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ] sys-devel/binutils-2.18-r1 [2.16.1-r3] USE="-nls*"
[ebuild R ] sys-devel/gcc-3.4.6-r2 USE="-d% -hardened* -nls*"
[ebuild U ] sys-libs/glibc-2.6.1 [2.3.6-r5]
USE="-debug% -gd% -hardened* -nls* -vanilla%"
$ emerge -Du world
[..]
>>> Source unpacked.
>>> Compiling source
in /var/tmp/portage/sys-libs/glibc-2.6.1/work/glibc-2.6.1 ...
* Building multilib glibc for ABIs: x86 amd64
The log file says nothing more than the message above. I already tried to
reemerge binutils to be sure the linker was ok. That didn't help.
This is my first AMD64 system so I'm not yet into the multilib stuff -
perhaps I made an error by not specifying "hardened" and/or "multilib" as
USE-flag? But after reading through the archives, I thought they are both
not used as long as I take the right profile.
Below you find my make.conf and the output of emerge --info. Thank you for
reading!
error building glibc on amd64
