how to deploy the crosstool generated cross compiler

[Dan Kegel]

Yes, one would expect to be able to move the binaries!
It'll be nice that with gcc-3.3.3 and later, it will be possible
using --with-sysroot to configure them to have that nice property.
(And one of these days I'm going to try it out and make sure it works...
I haven't ever seen it in operation.)
- Dan

Ming Zhang wrote:
> Thanks for your reply. I read part of the script. But I assumed that
> even I install there, I can change to some other place as I wish. So I
> am wrong and came to this question. Thanks again.
> 
> ming
> 
> On Wed, 2003-11-12 at 14:54, Dan Kegel wrote:
> 
>>Ming Zhang wrote:
>>
>>>I have a question about how to deploy the cross compiler generated by
>>>crosstool.
>>>
>>>After I get one cross compiler, it is sth like
>>>/foo/crosstool-0.24/result/result/arm-unknown-linux-gnu/gcc-3.3.2-glibc-2.3.2/..
>>>i can compile the 2.4 arm kernel successfully.
>>>
>>>but after i moved it to /usr/local/arm/gcc-3.3.2-glibc-2.3.2/... and use
>>>it to compile kernel again.
>>>
>>>i fail at make dep, because it can not find 
>>>"/foo/crosstool-0.24/result/arm-unknown-linux-gnu/gcc-3.3.2-glibc-2.3.2/lib/gcc-lib/arm-unknown-linux-gnu/3.3.2/include"
>>>
>>>
>>>how to solve this issue? The previous cross compiler i used does not
>>>have this issue, I can place them where ever i want and just make sure
>>>it is in the search path.
>>
>>gcc-3.3.3, when it comes out, will have that nice relocatable property
>>you want.  Until then, the thing to do is to set PREFIX before running all.sh or crosstool.sh
>>to point to where you want the compiler to end up.
>>
>>Although this is clear enough if you actually read the shell scripts,
>>a lot of people have had the same question, so in the next release
>>I'll make it more obvious.
>>
>>- Dan



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