From: Sam Ravnborg <sam@ravnborg.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: timing problem with building bounds.h?
Date: Tue, 17 Feb 2009 07:08:50 +0100 [thread overview]
Message-ID: <20090217060850.GA21538@uranus.ravnborg.org> (raw)
In-Reply-To: <4999FEFF.8090907@xenotime.net>
On Mon, Feb 16, 2009 at 04:04:15PM -0800, Randy Dunlap wrote:
> 2 times today I had problems with kernel builds using
> O= and -j4 and include/linux/bounds.h being incomplete.
> (using 2.6.29-rc5)
>
>
> bounds.h was like this:
>
> #ifndef __LINUX_BOUNDS_H__
> #define __LINUX_BOUNDS_H__
> /*
> * DO NOT MODIFY.
> *
> * This file was generated by Kbuild
> *
> */
> /// blank line here was the end of the file;
>
>
>
> Is there something in top-level Kbuild or Makefile that
> would explain this?
Not that I know of...
If you can reproduce it could you try:
1) What is the content of kernel/bounds.s
2) The output when building the kernel
[Even without V=1 this may give a clue where it goes wrong]
Was this with O=... build btw?
Sam
next prev parent reply other threads:[~2009-02-17 6:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 0:04 timing problem with building bounds.h? Randy Dunlap
2009-02-17 6:08 ` Sam Ravnborg [this message]
2009-02-17 16:54 ` 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=20090217060850.GA21538@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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