Bug 182577

Summary:	sys-devel/crossdev-0.9.18-r2 - crossdev -t i586-pc-linux-gnu fails on AMD64 building glibc
Product:	Gentoo Linux	Reporter:	Jaak Ristioja <jaak>
Component:	[OLD] Core system	Assignee:	Gentoo Toolchain Maintainers <toolchain>
Status:	RESOLVED INVALID
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	cross-i586-pc-linux-gnu-glibc.log cross-i586-pc-linux-gnu-info.log cross-i586-pc-linux-gnu-glibc.log (gzipped)

Description Jaak Ristioja 2007-06-19 13:53:03 UTC

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

Comment 1 Jaak Ristioja 2007-06-19 13:54:59 UTC

Created attachment 122513 [details]
cross-i586-pc-linux-gnu-glibc.log

Comment 2 Jaak Ristioja 2007-06-19 13:55:56 UTC

Created attachment 122515 [details]
cross-i586-pc-linux-gnu-info.log

Comment 3 SpanKY gentoo-dev

2007-06-20 04:35:31 UTC

glibc-2.3.6 is not supported

Comment 4 Jaak Ristioja 2007-06-20 08:20:12 UTC

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

Comment 5 Jaak Ristioja 2007-06-20 09:44:17 UTC

Created attachment 122580 [details]
cross-i586-pc-linux-gnu-glibc.log (gzipped)

The new log, gzipped.

Comment 6 SpanKY gentoo-dev

2007-06-20 09:48:42 UTC

you incorrectly have USE=hardened without using a hardened profile

Comment 7 Jaak Ristioja 2007-06-20 10:15:13 UTC

(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?

Comment 8 SpanKY gentoo-dev

2007-06-20 17:27:27 UTC

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

Comment 9 Jaak Ristioja 2008-06-06 00:47:40 UTC

(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?