All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Tilman Schmidt <tilman@imap.cc>
Cc: linux-kernel@vger.kernel.org, josh@freedesktop.org
Subject: Re: [2.6.24-rc2] make C=1 killed by sparse 0.4 choking on kernel/sched.c
Date: Tue, 13 Nov 2007 12:41:35 +0100	[thread overview]
Message-ID: <20071113114135.GA30627@uranus.ravnborg.org> (raw)
In-Reply-To: <47398255.3030309@imap.cc>

> 
> I don't quite know what to make of this. It looks like a bug in
> sparse, but kernel/sched.c is perhaps not quite innocent either.
> Also it doesn't seem right that the entire kernel compilation
> aborts just because of a failed sparse run.
> 
> Opinions?

With "make C=1" you can always do "make kernel/sched.o"
And then continue with "make C=1"

It is on purpose it stops so you are forced to fix your bugs.
It is not designed with sparse errors in mind :-)

	Sam

      parent reply	other threads:[~2007-11-13 11:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 10:54 [2.6.24-rc2] make C=1 killed by sparse 0.4 choking on kernel/sched.c Tilman Schmidt
2007-11-13 10:58 ` Alexey Dobriyan
2007-11-13 11:41 ` Sam Ravnborg [this message]

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=20071113114135.GA30627@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=josh@freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tilman@imap.cc \
    /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.