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] |
Hello JML! > The problem is that Travis-ci just export a CC variable at the Using CC= is a very bad idea, which you already described. This is used by gnu make implicit rules and by some configure scripts, too. The solution is to use another environment variable. > So I am wondering if there is an easy way to choose which base > compiler we want for the host part? This is currently hard coded (detected my "which") by CT-NG, as far as I have analysed in the last couple of minutes. When you look to ".build/<compiler_to_build>/buildtools/bin" you will see a lot of short shell scripts. This are the tools (including the compiler) which is used by CT-NG to build all the host tools. This short scripts are generated by "scripts/crosstool-NG.sh" beginning at line 408. You will see some lines with "where=...". You could add the check for an environment variable (e.g.: CT_TOOL_BUILD_gcc, CT_TOOL_BUILD_as, ...), defining the tool location/name to use. Then define the environment variables for the tools you would like to override in the .travis.yml file. BR Jasmin ******************************************************************* On 09/28/2015 03:18 PM, Jean-Marie Lemetayer wrote: > Hi, > > I am currently testing Travis-ci and the needed configurations to do a > proper continuous integration. > > Travis-ci allow us to configure which C compiler we want to use (GCC > or CLANG) to build our project. I think it could be good to test if > crosstool-NG (the host part) can be build with both. > > The problem is that Travis-ci just export a CC variable at the > beginning of the build to configure the compiler. This is not good > because the CC variable interferes with the configure / Makefile used > in the build process (especially in the target parts) . And it can > replace a `arm-unknown-linux-gnueabi-gcc` into a `gcc` ... > > So I am wondering if there is an easy way to choose which base > compiler we want for the host part? > > Regards, > JML > > -- > For unsubscribe information see http://sourceware.org/lists.html#faq > -- 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] |