Re: linux/autoconf.h problem

[Marius Groeger <mgroeger at sysgo dot com>]

On Wed, 7 Jul 2004, Dan Kegel wrote:

> The arm folks feel violently that 'make defconfig' is a misfeature;
> there are so many variants of arm that there is no one default,
> is the argument IIRC.  So I'm not sure the patch is right,
> nor do I know what the right thing to do is.

This argument is definitely true for someone wanting to compile a
kernely. To what extent, however, does this affect the generation of
toolchains? In other words, does the toolchain, libc most likely,
depend on specific CONFIG_* options, and if so, which?

Maybe it would be a good idea to start collecting such critical CONFIG
switches on a per-arch basis, what do you think?

For completeness, besides the linux/autoconf.h file a toolchain also
requires linux/version.h. Obviously this is an arch invariant, though.
In addition, the include/asm link is needed.

Regards,
Marius

-- 
Marius Groeger <mgroeger@sysgo.com>           Project Manager
SYSGO AG                      Embedded and Real-Time Software
Voice: +49 6136 9948 0                  FAX: +49 6136 9948 10
www.sysgo.com | www.elinos.com | www.osek.de | www.imerva.com


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com