tech-userlevel archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Help needed with understanding of config(1) debug output

On Thu, Sep 27, 2018 at 16:20:50 +0800, Paul Goyette wrote:

> I've got a problem where something I've changed over the last six months
> (or more) on the [pgoyette-compat] branch has broken the release build
> for at least `` -m algor'' port.  For some unknown reason it is
> defining COMPAT_NETBSD32 in opt_compat_netbsd32.h even though the option
> is not selected in the kernel definition file.
> I've tried to understand the debug output from ``config -ddddd ...'' but
> I simply don't understand the output.  (The output looks more like it is
> intended to debug config(1) itself, and not for debugging issues with
> config's input files.)  I find the following snippet in the debug output
>    dependopts:326: debug: depend attr `COMPAT_NETBSD32'
>    dependopts:326: debug: option selected `compat_netbsd32'
>    dependopts:326: debug: depend `COMPAT_NETBSD32' searched
> This seems to indicate that attribute COMPAT_NETBSD32 was previously
> "needed" and therefore we need to include option `compat_netbsd32'.  But
> there is no earlier mention of COMPAT_NETBSD32 in the debug output.

You made EXEC_ELF32 depend on COMPAT_NETBSD32 and since you enable
EXEC_ELF32, it pulls in COMPAT_NETBSD32 that it now depends on.


Home | Main Index | Thread Index | Old Index