[Rpm-maint] [rpm-software-management/rpm] RFE: separate macros for host and target (Issue #2624)
Panu Matilainen
notifications at github.com
Tue Aug 22 08:39:39 UTC 2023
Anytime --target is used, there's an unresolvable ambiguity as to what a particular macro might mean, it could be either the host or the target, depending whether the platform file for the target happened to override it. If it did, then we can no longer locate paths on the build host based on macros, and if it didn't, various things like %optflags leak through where they shouldn't. Both issues are present in everyday noarch packages.
AFAICS the only means to resolve this ambiguity is to have separate sets of macros for the build host and the build target to allow explicitly expressing which one is desired. We already have %_host_cpu, %_target_cpu and friends, but the existing non-prefixed macros will need to point to *target* macros at all times to preserve compatibility with the existing mass of specs, so I dunno if it makes sense to add %_target_foo macros to duplicate it all (unless some kind of cheap aliasing mechanism is implemented). %_host_foo seems like a reasonable pattern for the rest.
Inspired by https://bugzilla.redhat.com/show_bug.cgi?id=2231727 and related madness.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2624
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/2624 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20230822/1fed9b97/attachment.html>
More information about the Rpm-maint
mailing list