mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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
Date: Mon, 30 May 2005 21:53:20 +0200	[thread overview]
Message-ID: <17051.28464.67012.631845@alkaid.it.uu.se> (raw)
In-Reply-To: <20050530192835.GK10441@stusta.de>

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

  reply	other threads:[~2005-05-30 20:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-30 19:28 Adrian Bunk
2005-05-30 19:53 ` Mikael Pettersson [this message]
2005-05-30 20:13   ` Adrian Bunk
2006-01-06 20:37 Adrian Bunk
2006-01-06 21:11 ` Willy Tarreau
2006-01-06 21:54   ` Adrian Bunk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17051.28464.67012.631845@alkaid.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®