Paul Mundt wrote:
Indeed, that's what I was intending on keeping around as a convention,
and simply overloading SRCARCH for the sh64 case. i386/x86_64 potentially
has the same issue though, and if the intent is to have a single ARCH for
both of them, I don't see how that would possibly work without
sacrificing randconfig.. unless the intended x86 convention is that one
compiler will happily handle both i386 and x86_64 without any difficulty?
Well, that *is* the normal thing on x86.
HOWEVER, I think the right thing for allyesconfig, allmodconfig,
randconfig, etc. is to be able to override specific variables. Right
now, one has to use indirection via a file, which is a bit clumsy; it
would be better if one could do "make allyesconfig CONFIG_X86_64=y" or
somesuch.
In fact, we should be able to get rid of ARCH entirely; CONFIG_ options
have the huge advantage that they're saved in a file, and you don't have
to type them on every make run. The only option that I can't see us
getting rid of easily is HOSTCC, since it is used before config is run,
but probably something clever can be done there, too.
-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
