On Sat, Jan 09, 2021 at 08:15:36PM -0500, John Scott wrote:
> On Thursday, January 7, 2021 11:54:19 AM EST Bill Allombert wrote:
> > The issue is that using $(CC) breaks reproducible build due to pari.cfg.
> Are you referring to building Debian binary packages reproducibly as in [1]?
> I don't understand the connection. I see that the C compiler, architecture, 
> and other system information gets into pari.cfg, but the buildd's don't do 
> cross builds. Like Clang rebuilds, cross builds are still experimental 
> territory and will be for the foreseeable future.

I assume there is little purpose of doing rebuilds if the resulting
packages are not functionnal.

The problem with your proposal is that the resulting cross pari.cfg might not
actually work in a non-cross environment (mainly the package pari-gp2c).
For example the package produced with the clang rebuild would not work on
a machine where clang is not installed, because gp2c-run would call
clang instead of gcc.

For that reason, I used a neutral name (cc) for the compiler so that users
are not required to use a specific version of gcc or clang.

One fix could be to use sed to fix pari.cfg after 'make install'

An alternative would to set PATH so that cc is the cross compiler.

> It's normal for package builds to honor the CC variable. dh_auto_configure 
> does 
> this by default. I don't think the cross and reproducible builds initiatives 
> are incompatible. If I'm on the wrong track, could you explain how the change 
> would break reproducible builds so I can make an alternative fix?

I do not think there is an incompatibility, quite the opposite.
Using reproducible build, one could check that all non-binary files in
a package are identical between the cross-build and non-cross build
package.

For reproducible build, one should get identical binaries if CC is unset
or set to cc, gcc gcc-10, x86_64-linux-gnu-gcc as long as they are all
different names for the same binary, so hard-coding $(CC) in pari.cfg is
not working.

Cheers,
-- 
Bill. <ballo...@debian.org>

Imagine a large red swirl here. 

Reply via email to