Re: toolchain/59512: atari crunched binaries from reproducable builds contain source dir paths

["Martin Husemann via gnats" <gnats-admin%NetBSD.org@localhost>]

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

From: Martin Husemann <martin%duskware.de@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: toolchain/59512: atari crunched binaries from reproducable
 builds contain source dir paths
Date: Tue, 8 Jul 2025 09:41:49 +0200

 On Mon, Jul 07, 2025 at 07:40:01PM +0000, Harold Gutch via gnats wrote:
 >  does adding "-V MKREPRO=yes" to the build.sh call make any difference?
 >  
 >  For me with a similar build.sh invocation as the one from the build
 >  cluster (just with -O instead of -D/-M/-R/-T) I see the same without
 >  -V MKREPRO=yes, but if I add -V MKREPRO=yes it looks as expected.
 >  
 >  I haven't looked at this enough to say why this is not needed for
 >  other archs...
 
 We have -P on the command line and the docs say:
 
     -P             Set MKREPRO and MKREPRO_TIMESTAMP to the latest source
                    CVS timestamp for reproducible builds.
 
 however, we do pre-set MKREPRO_TIMESTAMP already (as the buildmaster
 has done that dance already and [depending on SCM in use] the clients
 might not be able to repeat it in our setup).
 
 According to the source the only thing that -P does is MKREPRO=yes
 
 So I am confused.
 
 Martin