Re: toolchain/58089: MKREPRO isn't really reproductible

[Manuel Bouyer <manuel.bouyer%lip6.fr@localhost>]

On Fri, Mar 29, 2024 at 01:23:29PM +0000, Taylor R Campbell wrote:
> > Date: Fri, 29 Mar 2024 13:10:00 +0000 (UTC)
> > From: Manuel Bouyer <Manuel.Bouyer%lip6.fr@localhost>
> > 
> > 	cvs co -r netbsd-10 -D "2024-03-26 19:10 UTC" -P src
> > 	cd src && ./build.sh -m i386 -P tools kernel=GENERIC
> 
> It looks like, for the i386 netbsd-10 autobuilds, we use:
> 
> -P -x -N0 -V TMPDIR=/tmp -V BUILD=yes -V MAKECONF="${AB_HOME}/etc/make.conf" -V MKDEBUG=yes
> 
> where ${AB_HOME}/etc/make.conf has (unnecessarily, I think):
> 
> MKREPRO=yes
> 
> I have no idea what BUILD=yes does, and it doesn't seem to be
> documented in share/mk/bsd.README (but it is _listed_ there and in
> BUILDING.mdoc), but -V MKDEBUG=yes is probably the difference.
> 
> We should have this information published somewhere so that others can
> verify it.

Thanks. Indeed with MKDEBUG=yes the kernel doens't have debug_info
(it's counterintuitive :)
BUILD=yes doens't seem to change anything for the kernel.

There is still a difference of 96 bytes between my kernel and the
official one. strings(1) shows this which may be relevant:
-_CFG_### START CONFIG FILE "/local/armandeche2/netbsd-10-20240326/src/sys/arch/i386/conf/GENERIC"
+_CFG_### START CONFIG FILE "GENERIC"

I didn't find how config(1) could generate a config_file.h without absolute
path.

-- 
Manuel Bouyer, LIP6, Sorbonne Université.           Manuel.Bouyer%lip6.fr@localhost
     NetBSD: 26 ans d'experience feront toujours la difference
--