Re: Custom kernel builds failing w/undeclared identifiers?

["John D. Baker" <jdbaker%mylinuxisp.com@localhost>]

On Thu, 23 Nov 2017, Paul Goyette wrote:

> > There was a recent change to config(1) and (I think) a bump in the
> > grammar version for config(5).  See
> > 
> > http://mail-index.netbsd.org/source-changes/2017/11/19/msg089808.html

As this appears to deal with "ioconf", it appears to be a suspect.
In each case, the device complained about is defined in the respective
included GENERIC kernel config and not elided in the custom config.

All the standard kernels build just fine.  In the amd64 case, the first
of my custom kernels builds (has "tpm at isa" elided as it does not have
one), but the second, which does have "tpm at isa" (defined in GENERIC
and not elided in the custom config) fails.

I'll try rolling this change back and seeing if that works.  I'm puzzled
by what about my configs is confusing it, though.

> And several others shortly preceeding the above, all the way back to
> 
> http://mail-index.netbsd.org/source-changes/2017/11/18/msg089791.html

This change fixed the infinite loop problem.  My last successful build
was just after this was committed.

-- 
|/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
|\ / jdbaker[snail]mylinuxisp[flyspeck]com    OpenBSD            FreeBSD
| X  No HTML/proprietary data in email.   BSD just sits there and works!
|/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645