> On Sat, Aug 19, 2006 at 02:48:14AM +0400, Solar Designer wrote:
> > We're about to migrate Openwall GNU/*/Linux (Owl) from its current gcc
> > 3.4.5 (which we used in our 2.0 release) to gcc 4+ - and we'd rather
> > _not_ migrate to Linux 2.6 at the same time, if we can. We'd be more
> > comfortable migrating to Linux 2.6 a few months later.
On Sat, Aug 19, 2006 at 01:11:15AM +0200, Adrian Bunk wrote:
> Considering that it's really easy to compile the kernel with a different
> compiler than the userland,
We want our end users to be able to rebuild all of Owl (including the
kernel) from source using only tools that are a part of Owl, yet we do
not want to be providing multiple versions of gcc (or of any other
package, for that matter). We've been successful at not providing
multiple versions of development tools and libraries so far - keeping
the system small and clean, yet fully self-rebuildable.
> do you _really_ want to use such a
> relatively untested kernel/gcc combination for a server platform?
I expect that we will fully move to Linux 2.6 before our next release,
but being able to move to gcc 4+ in Owl-current first simplifies our
development process. (And, yes, we've got end users of Owl-current who
will be recompiling kernels.)
Also, I expect this kernel/gcc combination to receive quite some testing
soon, if/once it becomes supported.
Alexander
-
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]