lkml.org 
[lkml]   [2000]   [Sep]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Linus writes ...

mec> (2) Make the architecture a configuration variable (!)

linus> Why?

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
multiple platforms.

> 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.

Michael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:38    [W:0.040 / U:1.652 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site