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, Notice that the compiler you are referring to below is called i686-build_pc-linux-gnu-g++, not i686-zm-linux-gnu-g++. The build_pc part indicates that the compiler mentioned below is the compiler used to build the cross-compiler, not the cross-compiler itself. This is why it is just a shell script that invokes your host compiler in /usr/bin. On 12/30/2013 06:34 PM, Mau Z wrote: > Hi again, > > Thanks for the quick advice. > > Do you mean that I should put : > BR2_TOOLCHAIN_EXTERNAL_PATH="/home/zm02/development/crosstoo-ng/crosstool-ng-1.18.0/toolChain/.build/i686-zm-linux-gnu/build/build-cc-final/gcc/ > > I tried it, but it did not work. > > Does crosstool-ng produce g++ for the target ??? > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > I am asking because the following file "i686-build_pc-linux-gnu-g++" > is actually a script which activated /usr/bin/g++ > Here is the content of this file : > #!/bin/bash > exec '/usr/bin/g++' "${@}" > > The file "i686-build_pc-linux-gnu-gcc" (which is located in the same > directory), is similar : > #!/bin/bash > exec '/usr/bin/gcc' "${@}" > > > Now if you compare it to "i686-zm-linux-gnu-gcc" (which is located in > the same directory), then this is a "real program" > ls -l i686-zm-linux-gnu-gcc > -rwxr-xr-x 2 User_01 User_01 1454560 Dec 30 08:50 i686-zm-linux-gnu-gcc > But there is no file named "i686-zm-linux-gnu-g++" > > > > > Thanks again > Mau -- 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] |