Comment # 26 on bug 1223967 from Egbert Eich

(In reply to Atri Bhattacharya from comment #24)
> 
> The attempt in obs://home:badshah400:lapackv3/lapack is to generate the
> x86-64-v3 libs purely as a separate flavour, *without* the baselibs.conf
> coming into play at all in so far as these -v3 libs are concerned.
> 
> Baselibs.conf is still used to produce 32-bit biarch packages for pure
> x86_64 in this case, but it simply does not matter for x86-64-v3 flavour
> since there aren't i586-v3 equivalents.
> 
> But perhaps I misunderstand your question?

No, you don't. What confused me: you were using the %suse_build_hwcaps macro -
which you have removed since. The problem I see is: this macro is crafted to
add the right 'magic' to the spec file (see
https://en.opensuse.org/openSUSE:Packaging_Conventions_RPM_Macros#%{?suse_build_hwcaps_libs}).
This magic is "to automatically set specific build targets and schedule the job
on workers which match the intended buildconstraint". Unfortunately, one can
only guess how this works. Without baselibs.conf, two arch flavors will be
built: x86_64 and x86_x6_v3. So I would think if you want to use flavors, you'd
need to add:
#!BuildTarget: x86_64_v3-linux
#!BuildConstraint: hardware:cpu:flag x86-64-v3
to the spec file in the -v3 flavor on x86_64. When using baselibs.conf for -v3,
 mkbaselibs will create a spec file which consumes these packages and
'repackages them into the main architecture'. You may need to do all this
manually.
I'm currently trying to figure out how all this works.