mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Herbert Rosmanith <kernel@wildsau.enemy.org>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>, linux-kernel@vger.kernel.org
Subject: Re: gcc-4.1.1 and kernel-2.4.32
Date: Wed, 21 Jun 2006 20:29:20 +0100	[thread overview]
Message-ID: <200606212029.20032.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <200606211425.k5LEPtY6012550@wildsau.enemy.org>

On Wednesday 21 June 2006 15:25, Herbert Rosmanith wrote:
> > In effect (mainline) no. Linux 2.2 and 2.0 won't be fixed for the same
> > reason; called deep maintenance. 2.6 has been on the road since Dec 2003,
> > that's over 2 years. Do away with the old stuff.
>
> we are in the process of switching, which is not unproblematic. on
> the other hand, we have to support existing installations as well.

FWIW, distributions generally let you install older GCCs. Hopefully your 
distribution still has 2.95.3 in its repository, so you could install this to 
get a well tested (and probably smaller code generating) compiler for 2.4 
kernels. gcc -V <version> can be used to switch between them, if your 
distributor opts to install to the same prefix.

-- 
Cheers,
Alistair.

Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.

  reply	other threads:[~2006-06-21 19:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 13:17 Herbert Rosmanith
2006-06-21 13:20 ` Herbert Rosmanith
2006-06-21 13:47   ` Michal Piotrowski
2006-06-21 14:18 ` Jan Engelhardt
2006-06-21 14:25   ` Herbert Rosmanith
2006-06-21 19:29     ` Alistair John Strachan [this message]
2006-06-21 19:33     ` Jesper Juhl
2006-06-21 14:11 Mikael Pettersson

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=200606212029.20032.s0348365@sms.ed.ac.uk \
    --to=s0348365@sms.ed.ac.uk \
    --cc=jengelh@linux01.gwdg.de \
    --cc=kernel@wildsau.enemy.org \
    --cc=linux-kernel@vger.kernel.org \
    /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®