On Tue, Apr 19, 2016 at 9:47 AM, Rob Savoye <rob.sav...@linaro.org> wrote: > On 04/18/2016 09:08 PM, $rik@nth wrote: > >>>> `../abe.sh --set arch=armv7-a --host arm-linux-gnueabi --target >>>> arm-linux-gnueabi --build all`.. Still observing the same issue while >>>> building libgcc > >>> You'd need to first build a arm-linux-gnueabi cross compiler, >> Here i am failing to build arm-linux-gnueabi cross compier for ARM > > For the x86_64 hosted cross compiler, just do this: > ../abe.sh --target arm-linux-gnueabi --build all
How to generate ARM instead of x86_64 - arm. Currently it is doing x86*->arm. Which i can not run them on ARM processor development board. > > It doesn't matter whether this is statically or dynamically linked at > all, it's just to compile the next step. > > It you really want to hack this into existence, I'll note that ABE > sets everything up so you can also do manual builds. All the component > builds are located in builds/$host/$target. I commonly do an ABE build, > then cd into a build directory and tweak configure flags, make flags, > etc... The nice thing is that ABE has built all the dependencies, like > binutils, etc... so you only have to hack on one part of the build, like > GCC. You an always manually add --disable-shared --enable-static if you > want. The existing configure options are in the top of config.log. so > it's all easy cut & paste. I do this frequently when debugging ABE. earlier i used to generate arm gcc static using above flags. But i am getting few LD erros as it failed to get them from right location > If you want to package the binary toolchain after building it, just > add --tarbin when running ABE, and it'll make a tarball you can just > install. That should also work for the ARM GCC executables, although > I've never tested that. > > - rob - > -- Thanks & Regards, M.Srikanth Kumar. _______________________________________________ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org https://lists.linaro.org/mailman/listinfo/linaro-toolchain
