Re: misc/52997: Build logs from successful builds contain "fatal error"

[Valery Ushakov <uwe%stderr.spb.ru@localhost>]

The following reply was made to PR misc/52997; it has been noted by GNATS.

From: Valery Ushakov <uwe%stderr.spb.ru@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: misc/52997: Build logs from successful builds contain "fatal
 error"
Date: Sat, 10 Feb 2018 18:16:53 +0300

 This happens when we generate kdump-ioctl.c - which we do four times,
 { kdump, ktruss } x { normal, rescue }.  src/usr.bin/kdump/mkioctls
 runs CC with only DESTDIR includes and we don't install osnet compat
 stuff.
 
 I'm not sure what's the right thing to do here.  Adding osnet includes
 to the path is quite intrusive as we will run into namespace issues.
 
 Perhaps the easiest way is to provide fakes for the mkioctl run.  We
 only need to provide empty
 
   ctf_api.h
   linker.h
   modctl.h
   processor.h
 
 With these added the CC invocation in mkioctl completes without errors
 and the generated kdump-ioctl.c file also contains the dtrace ioctls.
 
 -uwe