Skip to contentSkip to conversation

timing problem with building bounds.h?

DISCUSSION Randy Dunlap 2 participants 3 messages Feb 17, 2009 Kbuild

lore
Share & tools
lore
#0 lore raw

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?

Thanks,
~Randy

#1 lore raw
Quoted 15 lines · Randy Dunlap

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
*
*/

Quoted 6 lines
	/// 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

#2 lore raw
Quoted 20 lines · Sam Ravnborg
Quoted 19 lines · Randy Dunlap

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;
Quoted 8 lines
Quoted 2 lines

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]

I'll let you know if I can do that.

Quoted 1 line

Was this with O=... build btw?

Yes (see my 2nd line of text body :).

Thanks,
~Randy