On Wed, May 09, 2012 at 08:33:53AM +0200, Bernhard Reutner-Fischer wrote: > On 9 May 2012 05:24, Mike Frysinger <vap...@gentoo.org> wrote: > > On Tuesday 08 May 2012 13:53:55 Bernhard Reutner-Fischer wrote: > >> --- a/Makefile.help > >> +++ b/Makefile.help > >> - @echo ' CROSS_COMPILE= - Override CROSS_COMPILER_PREFIX from > > .config' > >> + @echo ' CROSS_COMPILE= - Override CROSS_COMPILER_PREFIX from > >> .config' > >> + @echo ' CROSS= - Same as CROSS_COMPILE' > > > > we dropped all mention of CROSS were possible on purpose. the only reason > > CROSS_COMPILE defaults to CROSS is because we didn't want to break peoples > > build scripts. if we're going to start adding info again, i say scrub it > > completely. > > I have reverted this inappropriate commit, let's keep the > backward-compatible var for a while though. > Thanks for the review!
Would it be possible to head in the direction of not neeting CROSS_COMPILE/CROSS? That is, make it so the build system just works with cross compiling as long as CC is set to the right compiler? I can think of a few potential issues like the way stripping is performed that might need a cross-specific tool other than CC, but perhaps there's a way to use -dumpmachine and determine if the results are native or cross, and automatically search out the rigth tools based on that. BTW this is all just an idea; if it's not feasible, there's no need for flames. Rich _______________________________________________ uClibc mailing list uClibc@uclibc.org http://lists.busybox.net/mailman/listinfo/uclibc