Dne 21. 12. 21 v 11:01 Florian Weimer napsal(a):
* Vít Ondruch:Since you are digging into this and AFAIK you are involved with toolchains, this reminds me this dreaded issue: https://bugzilla.redhat.com/show_bug.cgi?id=1284684 In short, various languages, such as Ruby embeds the build time options and reuse them for build of extensions. And I wonder, would it be possible to generalize this e.g. into some tool, which would set the environment variables and would be usable outside of rpmbuild?We have added %extension_… macros for the options that are safe to hard-code. But it doesn't solve the actual issue. The problem is not that it is difficult to get the flags, the issue is that we simply can't get the extension builders to move away from hard-coding them. If we add another mechanism, it will be as Fedora-specific as `rpm --eval %build_cflags` is today.
That is why I call out Tom and every other toolchain developers to provide more generic solution :) We should not solve the issue just on packaging level, but also for other developers. Everybody (on Fedora, but also elsewhere) should be able to benefit from the hard work which went into figuring out the best set of build flags.
Vít
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
