Bug 17858

Summary:	possible portage changes for cross-compiling
Product:	Portage Development	Reporter:	James Boddington (RETIRED) <aiken>
Component:	Core	Assignee:	Portage team <dev-portage>
Status:	RESOLVED FIXED
Severity:	normal	CC:	gcc-porting, lisa, mholzer, radek, zwelch
Priority:	High
Version:	2.0
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:	18024, 18031, 18033, 18034
Bug Blocks:	8450
Attachments:	uses the correct strip based on $CHOST uses the correct strip when cross compiling

Description James Boddington (RETIRED) gentoo-dev

2003-03-20 03:26:56 UTC

When using emerge for cross compiling portage uses the wrong strip when the package is installed. 
This renders any libs produced by the package unusable. 

Reproducible: Always
Steps to Reproduce:
1. host system is i686-pc-linux-gnu 
2. CHOST=sparc-unknown-linux-gnu ROOT=/tmp/cross emerge arch-sparc/glibc 
3. 
Actual Results:  
In this case the resulting glibc is useless because portage uses the wrong strip. 

Expected Results:  
If the correct strip is used (sparc-unknown-linux-gnu-strip) the resulting glibc is fine. This is just an 
example, but is has been a problem with other libs I have cross compiled. 

I have placed CBUILD=i686-pc-linux-gnu in make.conf so it is always the correct value. To get the 
correct strip used I modifed /usr/lib/portage/bin/prepallstrip such that if $CBUILD != $CHOST it 
uses $CHOST-strip instead of strip.

Comment 1 James Boddington (RETIRED) gentoo-dev

2003-03-20 03:29:42 UTC

Created attachment 9629 [details]
uses the correct strip based on $CHOST

This version of /usr/lib/portage/bin/prepstrip uses the correct strip if cross
compiling.

Comment 2 James Boddington (RETIRED) gentoo-dev

2003-03-20 03:37:28 UTC

Created attachment 9630 [details]
uses the correct strip when cross compiling

Give this another go. Just updated portage and lost my changes.

Comment 3 SpanKY gentoo-dev

2004-12-05 19:36:30 UTC

got carpaski to fix this today