[Rpm-maint] [rpm-software-management/rpm] %buildarch does not reflect architecture of current %package declaration (#689)

[Jason Tibbitts]

I'm trying to better understand how %buildarch works in the case of multiple %package declarations.  For more context, see https://bugzilla.redhat.com/show_bug.cgi?id=1705656

Basically, it appears that as soon as BuildArch: noarch is seen anywhere, the value of %buildarch changes to "noarch" and is never reset.  This means that a macro expanded within a %package declaration can't reliably tell if the package currently being defined is arch-specific or not.

Looking at the source, I can see the `case RPMTAG_BUILDARCHS` stanza in build/parsePreamble.c but I don't understand how the %buildarch macro gets set.  My uneducated guess is that it simply doesn't get reset when a new %package declaration is seen.  But I could also simply be completely failing to understand how macro expansion interacts with %package declarations.

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