https://bugzilla.novell.com/show_bug.cgi?id=795594 https://bugzilla.novell.com/show_bug.cgi?id=795594#c2 Richard Biener <rguenther@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adrian@suse.com, | |coolo@suse.com, | |rguenther@suse.com, | |ro@suse.com AssignedTo|rguenther@suse.com |mls@suse.com --- Comment #2 from Richard Biener <rguenther@suse.com> 2013-01-02 10:06:47 UTC --- Well, this is a generic issue in how we handle multilibs in BuildRequires (which get translated to Requires of the source package) and the fact that we only ship one source package. The BuildRequires: glibc-devel-32bit of the gcc47 source package gets magically translated to an appropriate architecture specific BuildRequires (nothing for x86 for example, glibc-devel-64bit for ppc for example). Due to the fact that we (randomly?) pick a source package from any architecture you sometimes get superfluous (or even bogus) requires in source packages. I believe the correct solution is to get rid of the magic translations and use (SUSE specific) macros here that are properly expanded on the host architecture and provided by rpm[build] macro files. Thus, instead of the above, have BuildRequires: glibc-devel-%multi or even BuildRequires: %glibc-devel-multi or BuildRequires: %multi(glibc-devel) which would select all available multilib variants for glibc-devel (if we ever again end up with more than two, like when we ever ship the new 32bit x86_64 multilibs). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.