Linus writes ...
mec> (2) Make the architecture a configuration variable (!)
The real reason is that it's the right thing to do. Part of a
configuration is "what machine it's for".
Here are some benefits:
(a) Arjan's testing machinery would catch problems in all architectures,
not just the x86.
(b> The sparc / sparc64 people can manage their builds a lot easier.
(c) With separate source and build trees, which I've implemented,
it becomes a lot more feaasible to manage kernel builds for
> Hey, maybe you have a few 18GB disks lying around, but none of the
> machines I use every day could afford to have another 5-6 cross-
> compilation environments lying around. It's just not practical.
So don't do it. You build with your favorite configuration, and I'll
build with my favorite 100 configurations.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Sep 07 2000 - 21:00:26 EST