Description of problem: When I try to run the first example in the "Fenics book" : python -c 'import dolfin ; u0 = dolfin.Expression("1 + x[0]*x[0] + 2*x[1]*x[1]")' ... I get an error : /usr/include/dolfin/function/Expression.h:25:10: fatal error: ufc.h: No such file or directory Version-Release number of selected component (if applicable): python3-dolfin-2019.1.0.post0-30.fc36.x86_64 dolfin-2019.1.0.post0-30.fc36.x86_64 dolfin-devel-2019.1.0.post0-30.fc36.x86_64 python3-dijitso-2019.1.0-9.fc36.noarch python3-ffc-2019.1.0.post0-8.fc36.noarch How reproducible: Every time Steps to Reproduce: 1. python -c 'import dolfin ; u0 = dolfin.Expression("1 + x[0]*x[0] + 2*x[1]*x[1]")' 2. :-( 3. Actual results: ------------------- Start compiler output ------------------------ In file included from /tmp/tmpupqqenu_/dolfin_expression_c49ebd8fd6c25a3c31b612f2a1752a2c.cpp:13: /usr/include/dolfin/function/Expression.h:25:10: fatal error: ufc.h: No such file or directory 25 | #include <ufc.h> | ^~~~~~~ compilation terminated. ------------------- End compiler output ------------------------ Compilation failed! Sources, command, and errors have been written to: /tmp/jitfailure-dolfin_expression_c49ebd8fd6c25a3c31b612f2a1752a2c Traceback (most recent call last): File "/usr/lib64/python3.10/site-packages/dolfin/jit/jit.py", line 165, in compile_class module, signature = dijitso_jit(cpp_data, module_name, params, File "/usr/lib64/python3.10/site-packages/dolfin/jit/jit.py", line 47, in mpi_jit return local_jit(*args, **kwargs) File "/usr/lib64/python3.10/site-packages/dolfin/jit/jit.py", line 103, in dijitso_jit return dijitso.jit(*args, **kwargs) File "/usr/lib/python3.10/site-packages/dijitso/jit.py", line 216, in jit raise DijitsoError("Dijitso JIT compilation failed, see '%s' for details" dijitso.jit.DijitsoError: Dijitso JIT compilation failed, see '/tmp/jitfailure-dolfin_expression_c49ebd8fd6c25a3c31b612f2a1752a2c' for details During handling of the above exception, another exception occurred: Traceback (most recent call last): File "<string>", line 1, in <module> File "/usr/lib64/python3.10/site-packages/dolfin/function/expression.py", line 400, in __init__ self._cpp_object = jit.compile_expression(cpp_code, params) File "/usr/lib64/python3.10/site-packages/dolfin/function/jit.py", line 158, in compile_expression expression = compile_class(cpp_data, mpi_comm=mpi_comm) File "/usr/lib64/python3.10/site-packages/dolfin/jit/jit.py", line 170, in compile_class raise RuntimeError("Unable to compile C++ code with dijitso") RuntimeError: Unable to compile C++ code with dijitso Expected results: Additional info: Dunno what the problem is. FYI, there is a ufc.h file in python3-ffc : /usr/lib/python3.10/site-packages/ffc/backends/ufc/ufc.h Also, I notice in dolfin-devel, there is a /usr/lib64/pkgconfig/dolfin.pc file ...
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
FEDORA-2023-c10572342c has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-c10572342c
FEDORA-2023-4203d8d813 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-4203d8d813
FEDORA-2023-c10572342c has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-c10572342c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-c10572342c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-4203d8d813 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-4203d8d813` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-4203d8d813 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-4203d8d813 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-c10572342c has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.