> Maybe I'm missing something fundamental here, but I don't understand how is
> -flto=auto supposed to help with making builds more reproducable.
Because if you are given a builder with 8 cores:
```
[ 40s] + export 'CFLAGS=-O2 -Wall -D_FORTIFY_SOURCE=2
-fstack-protector-strong -funwind-tables -fasynchronous-unwind-tables
-fstack-clash-protection -Werror=return-type -flto=8 -g'
```
Then `rpm -qp --qf "%{OPTFLAGS}" $rpm` will show you the `-flto=8` and that's
the problem for reproducibility.
> In rpm context, the number of cpus make uses is typically set by rpm (whether
> configuration or "all available"), and if you let it fall back to "as many as
> possible" then it's just as system dependent as the current rpm set method,
> no?
Yes, except we can communicate with `make` job server and run tasks
dynamically. And if not, then we'll do the same. Except we'll not have issues
with reproducibility.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/809#issuecomment-520397317_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
