Dne 24. 12. 22 v 20:49 Florian Weimer napsal(a):
* Vít Ondruch:
> Working with upstream on one issue [1], it seems that the culprit is in
> the Fedora compiler options. Is there some convenient way to set them
> up? Of course I can copy them from log, or somehow put together from the
> RPM macros, but I'd appreciate if there was some easier way. Can we e.g.
> distribute some script, which would set them up, as part or some RPM?
Build systems and test harnesses often tweak the build flags, so it's
probably best to enable logging there to see what's going on.
Of course the build flags can be seen from the build log, but precisely
for the reason that "Build systems and test harnesses often tweak the
build flags", I'd like to have easy way to provide upstream with the
default Fedora build flags.
Different distributions also have different compiler defaults. For
example, most of Fedora's explicit compiler flags are enabled by
default in Ubuntu's GCC.
And yes, that is the problem why upstream can't see the issues we see,
despite they were so kind to test on Fedora. Luckily, there was analysis
of the issue which initially triggered this discussion done by Mamoru
[1] and it seem that the issue are caused by LTO. Nevertheless, if there
was some way to tell them lets say:
1) $ sudo dnf install fedora-official-build-flags
2) $ with-fedora-official-build-flags make
That would be super convenient and I still find surprising we don't have
anything like this.
Vít
[1]
https://bugs.ruby-lang.org/issues/19248#note-14