MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17051.28464.67012.631845@alkaid.it.uu.se>
Date: Mon, 30 May 2005 21:53:20 +0200
From: Mikael Pettersson <mikpe@csd.uu.se>
To: Adrian Bunk <bunk@stusta.de>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
       linux-kernel@vger.kernel.org
Subject: Re: [2.4 patch] document that gcc 4 is not supported
In-Reply-To: <20050530192835.GK10441@stusta.de>
References: <20050530192835.GK10441@stusta.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1357
Lines: 38

Adrian Bunk writes:
 > gcc 4 is not supported for compiling kernel 2.4, and I don't see any 
 > compelling reason why kernel 2.4 should ever be adapted to gcc 4.
...
 > --- linux-2.4.31-rc1-full/init/main.c.old	2005-05-30 21:20:00.000000000 +0200
 > +++ linux-2.4.31-rc1-full/init/main.c	2005-05-30 21:21:19.000000000 +0200
 > @@ -84,6 +84,13 @@
 >  #error Sorry, your GCC is too old. It builds incorrect kernels.
 >  #endif
 >  
 > +/*
 > + * gcc >= 4 is not supported by kernel 2.4
 > + */
 > +#if __GNUC__ > 3
 > +#error Sorry, your GCC is too recent for kernel 2.4
 > +#endif
 > +
 >  extern char _stext, _etext;
 >  extern char *linux_banner;
 >  

This is redundant. Any attempt to compile vanilla 2.4 with gcc4
will fail with compilation errors. (And except for one issue on
x86-64 which actually was a kernel bug, those are the only known
issues with using gcc4 for 2.4.)

OTOH, for those of us that do use gcc4, this just gets in the way
and forces the gcc4 fixes kit for 2.4 to be even larger.

Since distributors won't use gcc4 for 2.4, and naive users won't
succeed anyway, what's the point?

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