In message <Pine.LNX.4.62.0605050940410.649@xxxxxxxxxxxxxxxxxxxx> you wrote: > > But on second thought: config options are part of the target configuration, > while CROSS_COMPILE= is part of the host configuration, so IMHO it doesn't > belong in Kconfig. I.e. do you want to have CONFIG_CROSS_COMPILE set in your > defconfig? Yes or no, depending on whether you do cross-compilations or not. So > you cannot simply take a defconfig, you'll have to modify it for your host > setup. CONFIG_CROSS_COMPILE is a terrible idea. Don't do it. We may want to try different tool chains which require different CROSS_COMPILE settings with exact the same default config file. Don't break this! > So I'd prefer to keep the CROSS_COMPILE, like other arches do. Me too! Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@xxxxxxx If A equals success, then the formula is A = X + Y + Z. X is work. Y is play. Z is keep your mouth shut. - Albert Einstein
