Failure to build on riscv64

Bug #2002486 reported by Heinrich Schuchardt
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fenics-dolfinx (Ubuntu)
Invalid
Undecided
Unassigned
openmpi (Ubuntu)
Fix Committed
Undecided
Unassigned

Bug Description

Building for riscv64 fails:
https://launchpad.net/ubuntu/+source/fenics-dolfinx/1:0.5.2-2/+build/25464074

The problematic line is in debian/patches/lib_rename.patch and was introduced in 1:0.4.1-1exp1.

Package libpetsc-complex3.18-dev_3.18.3+dfsg1-1_riscv64
file /usr/lib/petscdir/petsc3.18/riscv64-linux-gnu-complex/include/petscconf.h:

    #define PETSC_USE_COMPLEX 1

Package libpetsc-real3.18-dev_3.18.3+dfsg1-1_riscv64
file /usr/lib/petscdir/petsc3.18/riscv64-linux-gnu-real/include/petscconf.h:
PETSC_USE_COMPLEX 1 is not defined

It seems that for riscv64 we are somehow using the wrong header when calling check_symbol_exists().

pkg_search_module(PETSC REQUIRED IMPORTED_TARGET PETSc petsc)
does not specify if you are looking for the real or the complex version of the pkg-config file. Maybe setting CMAKE_PREFIX_PATH could help.

Tags: fr-3176
tags: added: fr-3176
Revision history for this message
Graham Inggs (ginggs) wrote :

This was fixed by https://launchpad.net/ubuntu/+source/openmpi/4.1.4-3ubuntu2

It looks like openmpi 4.1.4-3ubuntu1 built with pmix 4.1.2-2ubuntu2 on riscv64, but 4.2.2-1 on the other architectures.

Changed in fenics-dolfinx (Ubuntu):
status: New → Invalid
Changed in openmpi (Ubuntu):
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.