libnbd failed in the mass rebuild. I kicked off a second build by
hand, and it failed in the exact same way:
DEBUG util.py:623: Downloading Packages:
DEBUG util.py:621: Error: Error downloading packages:
DEBUG util.py:621: Cannot download toplink/packages/ocaml/4.11.0/0.4.dev2.fc33/s390x/ocaml-compiler-libs-4.11.0-0.4.dev2.fc33.s390x.rpm: All mirrors were tried
Is this a generic s390 problem of is there really something wrong with
the ocaml-compiler-libs package? If it's generic then I guess this
sort of error could be affecting a lot of other packages in the mass
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
Jakub Jelinek writes:
> For targets which do support the target attribute, each
> function should be marked with the right set of options
> before streaming it,
Looking at the source (opencv 4.3.0) I can not find any usage of
__attribute__ ((target)) or #pragma ... optimization associated with ppc
What I did find was a blind usage of
// absolute difference
# define vec_absd(a, b) vec_sub(vec_max(a, b), vec_min(a, b))
ie if vec_absd is defined use it otherwise fake it.
and vec_absd will be defined in altivec,h (for gcc 9/10) #ifdef
As I have found (repeatedly) this is not good enough. PVECLIB Building
<https://munroesj52.github.io/index.html#main_libary_issues_0_0> I suspect
this is another case that does not work when mixing targeted objects in LTO.
> Hello opencv  build also failed around LTO
Looking at the build logs:
For the build.log that ends with:
lto1: error: '__builtin_altivec_vadub' requires the '-mcpu=power9' option
lto1: fatal error: target specific builtin not available
The build uses a mix of compiler options.
-mcpu=power8 ... -mcpu=power9 -mtune=power9
I suspect this works at the level of individual object (*.o)
generation but this might cause problems when a mix of -mcpu=power8
and -mcpu=power9 objects are combined in LTO optimization.
The compiler might get confused.
Jeff Law wrote:
> For ppc64le is that the build was done with p8, but there is one
> function (__builtin_altivec_vadub) that requires p9. This seems
> like a package bug at first glance, not an LTO issue.
Yup __builtin_altivec_vadub is POWER9_VECTOR only.
For P8/6 use something like this:
vmin = vec_min (a, b);
vmax = vec_max (a, b);
result = vec_sub (vmax, vmin);
executes in 4 cycles.
Fmt package will be rebased in Rawhide from version 6.2.1 to 7.0.0 next
This will include soversion bump from 6 to 7. All dependent packages
must be rebuilt.
Please check your packages, because there are some breaking API changes:
Vitaly Zaitsev (vitaly(a)easycoding.org)