This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See crosstool-NG 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] |
Hi Thomas, I didn't set anything special, I think. I think, there has to be some setting I'm missing. Which settings do you have according sysroot? And if you call cross-gcc with --print-sysroot, do you get relative or absolute path? I get absolute path to the location I've used to build the toolchain.... Thanks for your help, Filipp On 17.06.2013 16:53, Thomas Petazzoni wrote: > Dear Filipp Andjelo, > > On Mon, 17 Jun 2013 14:40:32 +0000, Filipp Andjelo wrote: > >> I built a toolchain using crosstool-ng and it works fine, as far as I >> don't move it to another folder. I want to have a toolchain, which I can >> put everywhere, but how? >> If I run "gcc --print-sysroot", I get absolute path to the directory, >> where toolchain was built. If I check the same for google's Android >> toolchain, I get relative path >> to the gcc. How did they do that? >> >> Currently, I have a workaround using CFLAGS="--sysroot=path/to/sysroot", >> but It's not acceptable solution here. > Did you do some special configuration to Crosstool-NG? Because by > default, Crosstool-NG puts the toolchain sysroot is a correct location > that allows the toolchain to be relocatable. And it works well for me. > > Best regards, > > Thomas -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |