adding custom CFLAGS

Larry Brigman larry.brigman at gmail.com
Wed Oct 18 17:16:23 UTC 2006


On 10/18/06, Bernhard Fischer <rep.nop at aon.at> wrote:
> On Wed, Oct 18, 2006 at 12:24:53PM -0400, Rob Landley wrote:
> >On Wednesday 18 October 2006 12:25 am, Larry Brigman wrote:
> >> I have tracked down all my troubles to a tool chain issue.
> >> In using 1.1.2 I was able to use a custom CFLAGS variable
> >> that would allow me to point busybox to the cross compile tool
> >> chain includes and libraries.
> >>
> >> The current version does not allow these options.
> >
> >By "current version" to you mean 1.2.1, or svn?
1.2.1
> >
> >> How do I get that functionality back without reverting back
> >> to the older version?
> >
> >Hmmm...  We added ":=" to avoid recalculating lots of check_gcc() macros
> >(which is PAINFULLY slow, and largely there so Bernhard can keep an old Tru64
> >system upright through various necromantic rituals).  Unfortunately, this is
>
> ;) Well, i added the "hosttools" make target for Tru64, and i added the
> check_cc and check_ld to
> a) support several versions of gcc, each of which may support one flag
>    but not another
> b) to support folks that don't use gcc but other compilers
>
> Those two latter additions are not really entangled with True64, just as
> a sidenote.
>
> The current (i.e. svn) Make stuff currently does bomb a) as well as b)
> back to the stoneage, but i guess that's ok for a (re-)start of the
> build infrastructure. (anyone ran hosttools or check recently?)
>
>
> >overriding anything provided in environment variables, isn't it?
>
> You can say
> make EXTRA_CFLAGS="-my-fancy-flags" CROSS="i286-hurd-uclibc"
Do you need to do this on the command line for make oldconfig and make all?



More information about the busybox mailing list