public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Thomas Backlund <tmb@mandriva.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.34-pre1
Date: Fri, 18 Aug 2006 06:47:45 +0200	[thread overview]
Message-ID: <20060818044745.GN8776@1wt.eu> (raw)
In-Reply-To: <ec1c5j$5mu$1@sea.gmane.org>

On Thu, Aug 17, 2006 at 12:16:56PM +0300, Thomas Backlund wrote:
> Chris Rankin skrev:
> >>But maybe it's worth doing a user survey to find out what the users of
> >>2.4 want... (and with that I mean users of the kernel.org 2.4 kernels,
> >>people who use enterprise distro kernels don't count for this since
> >>they'll not go to a newer released 2.4 anyway)
> >
> >I have only one machine that is still running a v2.4 kernel (from 
> >ftp.kernel.org), and that is an
> >old P120 that I occasionally use as a wireless acess point.
> >
> >The compiler on this P120 is indeed gcc-3.4. However, building any kernel 
> >on that machine is now
> >so excruciatingly painful that I am considering using a newer, beefier 
> >machine as a build machine
> >instead. That machine is running FC5, and so uses gcc-4.1. So from my 
> >perspective, being able to
> >build a 2.4 kernel using gcc-4.x would be a benefit.
> >
> >
> 
> Why not simply set up chroots to build in ??

"simply" :-)
setting up a reliable build chroot is more difficult than just rebuilding
another gcc !

> Thomas

Regards,
willy


  reply	other threads:[~2006-08-18  4:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-17  7:57 Linux 2.4.34-pre1 Chris Rankin
2006-08-17  9:16 ` Thomas Backlund
2006-08-18  4:47   ` Willy Tarreau [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-16 22:36 Willy Tarreau
2006-08-16 23:54 ` Adrian Bunk
2006-08-17  5:16   ` Willy Tarreau
2006-08-17  6:48     ` Arjan van de Ven
2006-08-17  8:35       ` Andreas Steinmetz
2006-08-17  8:50         ` Mikael Pettersson
2006-08-17 12:48           ` Adrian Bunk
2006-08-17 20:43             ` Willy Tarreau
2006-08-17 23:41               ` Gerd v. Egidy
2006-08-18  4:40                 ` Willy Tarreau
2006-08-21  0:56               ` Adrian Bunk
2006-08-17  9:06         ` Adrian Bunk
2006-08-17  9:16           ` Andreas Steinmetz
2006-08-18 23:25             ` Adrian Bunk
2006-08-19  1:20               ` Grant Coady
2006-08-20 17:27                 ` Adrian Bunk
2006-08-19  4:45               ` Willy Tarreau
2006-08-21  0:35                 ` Adrian Bunk
2006-08-21  0:41                   ` Willy Tarreau
2006-08-21  1:07                     ` Adrian Bunk
2006-08-17  8:37       ` Willy Tarreau
2006-08-17  9:12 ` Thomas Voegtle
2006-08-18 22:48 ` Solar Designer
2006-08-18 23:11   ` Adrian Bunk
2006-08-18 23:27     ` Solar Designer

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=20060818044745.GN8776@1wt.eu \
    --to=w@1wt.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tmb@mandriva.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