Using sys-devel/crossdev-0.9.18-r2. * Emerging cross-glibc ... * glibc failed :( * If you file a bug, please attach the following logfiles: * /var/log/portage/cross-i586-pc-linux-gnu-info.log * /var/log/portage/cross-i586-pc-linux-gnu-glibc.log
Created attachment 122513 [details] cross-i586-pc-linux-gnu-glibc.log
Created attachment 122515 [details] cross-i586-pc-linux-gnu-info.log
glibc-2.3.6 is not supported
Then why did crossdev want to build glibc-2.3.6 by default? The following also fails when building glibc: crossdev --binutils 2.16.1-r3 --gcc 3.4.6-r2 --libc 2.5-r3 --kernel 2.6.17-r2 -t i586
Created attachment 122580 [details] cross-i586-pc-linux-gnu-glibc.log (gzipped) The new log, gzipped.
you incorrectly have USE=hardened without using a hardened profile
(In reply to comment #6) > you incorrectly have USE=hardened without using a hardened profile > Then shouldn't the profiles/default-linux/amd64/2007.0 profile automatically use.mask the hardened use-flag? I plan to use the cross-toolchain to help the hardened i586 box to build packages via distcc. I accidentally unmerged the toolchain I previously had for this, and had to re-crossdev. Btw, what does the hardened use-flag do, making the compile fail?
yes, ideally USE=hardened should be masked everywhere except the hardened profiled USE=hardened will cause gcc to be compiled differently and unless you're using a hardened profile, this will cause problems
(In reply to comment #8) > yes, ideally USE=hardened should be masked everywhere except the hardened > profiled > > USE=hardened will cause gcc to be compiled differently and unless you're using > a hardened profile, this will cause problems > However, can I use non-hardened GCC to make hardened binaries?
