mk_kernel error

[Rafael Brito]

Guys,
I've got this following message after mk_kernel command:
# Initializing
config: line not within a table boundary

And I can't recompiling my kernel!

What's going on?

Rafael

[Rick Garland]

For doing kernels builds, it is a good idea to use SAM for this because it will tell you if you have some parameters that are not within the constraints.

[John Palmer · Accepted solution]

Has anything changed in directory '/usr/conf/master.d' since you last built a kernel?

Perhaps you could post a listing with 'll'

Regards,
John

[Rita C Workman]

This may not be relevant in your case...I had kernel build problem (error code 71).
It would not build the kernel...and when I finally got it to build a kernel; it was unbootable. You can read the response to the other person (do a search: kernel build 71.....I think it's dated 8/29 or around there).
Anyway, in my case the problem turned out to be that one patch had somehow been install twice. The later version writing over the object files of some 34 patches.
When I ran check_patches it created the report /tmp/check_patches.report. I sent this to an HP Tech and HP was able to identify the patches that needed to be re-installed. I did this (one install in one giant depot).....and it worked. My kernel built and was totally bootable. It was alot of work...but it was fixed.
Like I said this may not be your solution.....but if your still looking, it's something to check out.
....ps check_patches is a utility of Ignite-UX
Regards,

[melvyn burnard]

you have a corrupt, or obsolete file inthe /usr/conf/master.d directory.
Go investigate what is in their, remove it and try again