[Rpm-maint] [rpm-software-management/rpm] Use -flto=auto as a default for _lto_cflags. (#809)

marxin notifications at github.com
Mon Aug 12 12:04:23 UTC 2019


> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20190812/b1a74935/attachment.html>


More information about the Rpm-maint mailing list