All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Rod Van Meter <Rod.VanMeter@nokia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: massive compile failures w/ 2.5.51 on RH8.0
Date: Fri, 13 Dec 2002 00:27:50 +0000	[thread overview]
Message-ID: <20021213002750.GB18156@suse.de> (raw)
In-Reply-To: <1039738018.1348.80.camel@dadhcp-172019068122.americas.nokia.com>

On Thu, Dec 12, 2002 at 04:06:59PM -0800, Rod Van Meter wrote:

 > At this point I've concluded that something in my setup is busted. 
 > Surely this large a fraction of things don't currently fail to even
 > compile?

This large a fraction of things don't currently compile.
And don't call me Shirley. 8-)

Seriously, you got unlucky, and seem to be hitting just about
every broken driver/filesystem there is in 2.5 right now.
If you take a look at bugzilla.kernel.org you'll see that
most of the compile errors noted there are those that you've
highlighted.

Things like Intermezzo don't affect a large proportion of users,
so remain broken for some time. The framebuffer changes in 2.5.51
fixed up a whole bunch of problems that had been lingering for
a while, but there's still a lot of drivers not converted over
to the new API.

Compile-time breakage is to be expected in 2.5.x. It's a hard-hat
area. You may have more luck with 2.5-ac.

		Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  reply	other threads:[~2002-12-13  0:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-13  0:06 massive compile failures w/ 2.5.51 on RH8.0 Rod Van Meter
2002-12-13  0:27 ` Dave Jones [this message]
2002-12-13  5:42   ` Randy.Dunlap
2002-12-13 12:20     ` Dave Jones
2002-12-13 23:05       ` Randy.Dunlap

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=20021213002750.GB18156@suse.de \
    --to=davej@codemonkey.org.uk \
    --cc=Rod.VanMeter@nokia.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.