Cross-compiling toolchain default location choice

Dan Kegel dank@kegel.com
Mon Oct 4 06:56:00 GMT 2004


ncrfgs wrote:
> On Sun, Oct 03, 2004 at 04:44:13PM -0700, Dan Kegel wrote:
> 
>>Those are good choices, appropriate e.g. for a G3 Power Mac.
>>What hardware are you planning to target?
> 
> 
> I would like to be able to run the code on 32 bit PowerPC architectures in 
> general.

Sorry, that's not possible.  See
http://www-106.ibm.com/developerworks/linux/library/l-powarch/
You have to choose a bit, I think.
Also note that the powerpc-405 requires special hacks to run
properly.  Those hacks are in gcc and glibc already (recent versions, anyway),
but you do have to configure for them specificially.

Can you be more specific about which 32 bit PowerPC chips you
want your apps to run on?

> There is surely a way to make crosstool to use a custom tarball but maybe, 
> given the way they are written and the aims it wants to achieve, this is not 
> what crosstool is good at.

On the contrary.  I told you exactly how to do that: drop the
custom tarball into crosstool's download directory.  The doc
should explain this; I'll add a note about it.

>>Another cure for that is to leave out *all* the patches, and only bring
>>in the patches one by one as you run into the problems they fix.
> 
> 
> With no risk I didn't mean I wanted a nuclear-proof cross-compiling toolchain, 
> of course. :D The only way to run no risk is doing nothing at all. =) I just 
> exactly meant no risk to have to run the script several times and bring in the 
> patches one by one as I run into problems. What if the problem a patch fixes 
> doesn't show at compile-time but only at run-time?

I suppose I could uniformly tag patches so you can recognize that easily.

>>Anyway, I like the guy who wrote the cross-lfs package, and I think
>>he did fine work.   I just want to make sure that I understand
>>why you like his stuff better than crosstool, so I can address
>>those problems.
> 
> 
> Sorry I didn't mean to make you upset.
> 
> You asked me to tell you more about the problems I faced with crosstool and to
> be more specific so I tried to. I didn't mean to tell you how to change
> crosstool but just to try to explain why I preferred cross-lfs over crosstool.
> 
> Those were just the feelings of a user.

I'm not upset, just trying to understand what it is you didn't
like about crosstool so I can fix it.
- Dan

-- 
My technical stuff: http://kegel.com
My politics: see http://www.misleader.org for examples of why I'm for regime change

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com



More information about the crossgcc mailing list