From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Moore Date: Tue, 07 Aug 2012 19:27:33 -0700 Subject: [Buildroot] building native gcc for target In-Reply-To: References: Message-ID: <5021CE95.9000808@sri.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On 8/7/12 7:19 PM, Steve Calfee wrote: > On Tue, Aug 7, 2012 at 6:18 PM, Kevin Broch wrote: >> I'm am looking to build a complete (gcc too) development environment on the >> target (arm) but currently don't see that this is possible. >> I have tried all 3 toolchain types (buildroot, cross-ng, external (linaro), >> but regardless I don't find gcc in output/target/usr/bin/gcc >> I am wondering if I am missing something? >> >> If not I am looking for any pointer on how I might do this (having never >> created a buildroot package). >> Ideally I would like to create a package that compiles Linaro GCC: >> https://wiki.linaro.org/WorkingGroups/ToolChain/Using/GCCNative >> I am imagining leveraging what is used to generate other tools like gdb, >> binutils, and trying to incorporate the various machine options (VFP, >> softfloat, etc) >> in the configure options. >> >> Any pointers would be appreciated. >> >> Best, / I guess you haven't seen how to do it because it is kind of bizarre. > You want to cross compile a native mode compiler. Why? > > Most people building embedded systems don't want to compile on those > systems. I don't know how you even bootstrap a gcc build in a system > without a c compiler. > > Regards, Steve > _______________________________________________ > buildroot mailing list > buildroot at busybox.net > http://lists.busybox.net/mailman/listinfo/buildroot According to http://www.uclibc.org/toolchains.html (which unfortunately seems quite out of date), this is a recommended way of creating a development system for using uClibc. I'm actually trying to do something similar to easily build applications in a "clean" environment with only uClibc headers, etc, and also having trouble. Has anyone done this recently? (See my message earlier today about a configuration for x86_64) Kevin, you may need to select GCC in the "package selection for target -> development tools" options in menuconfig (which requires setting development files on target to true in build options). I've gotten that far but the resulting native compiler hasn't worked reliably. Cheers, Scott