This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: how to deploy the crosstool generated cross compiler


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]