[package] gfortran/10.2: Missing files causing execution error #4696
Comments
|
Yes f951 is the actual compiler, it should be packaged with gfortran executable. Problem in this recipe: the "Linux" archive is not there anymore. And surprinsingly the recipe tries to download it even though I'm on Windows. |
|
This recipe is broken in another way: f951 has dependencies, and we probably don't want to put its vendored dependencies in lib folder of this package... On Macos: |
|
I've been digging into this for a little bit, and to summarise my findings, some of which I think are implied above but just to be explicit, this recipe has a number of problems:
Whilst not directly applicable to rectifying this, the Guide to Building gcc/gfortran should be illustrative of the requirements and process of building gfortran successfully. The pre-requisites can be summarised as follows:
The methods suggested to obtain these are:
It strikes me that the "difficult way" is probably what we should aim to achieve here? Mostly because this gives us proper isolation of the build artefacts from system files and conan would be responsible for populating those flags/variables when building and linking. The question is though, how far through the above list of requirements do we go before considering that the easiest/best solution here may just be to download pre-built binaries or expectation that the compiler/pre-requisite libs are pre-installed on the system? I know that a working fortran compiler is a blocker on a number of existing recipes, including: |
|
Conan Docker Tools provides new GCC images with fortran support. |
To clarify, it sounds like you mean that it's fine to specify gfortran as a system dependency because the CI now ships with it? If this is the case, perhaps it would be worth updating KB-H032 to reflect exceptions to this rule? |
|
In a conversation with @uilianries on slack, this is the current state of a gfortran compiler on the CI machines:
|
|
Not first time someone ask for Fortran, I'll revisit it on Friday (typically I fix recipes on Friday). |
|
@uilianries just checking, has fortran been made available on the CI runners? |
Yes, but for Linux docker images only, which are used on Conan Center. |
Is there a plan to add a fortran compiler to the windows runners? |
Actually the idea is package everything, so you can reproduce any scenario by adding a simple package. But of course, first we need to package fortran .... |
|
Looks like this can probably be closed by #12613? |
|
@samuel-emrys Yes. Now we are using pre-built version of gfortran, which fixes the original case. |
First appearance on #4681
There are some missing files in gfortran which are necessary its execution.
Package and Environment Details (include every applicable attribute)
Conan profile (output of
conan profile show defaultorconan profile show <profile>if custom profile is in use)Steps to reproduce (Include if Applicable)
Add Fortran as project in your CMake file:
add_project(foobar C++ Fortran)
Add
gfortran/10.2as requirementRun any Conan command which invokes build step.
Logs (Include/Attach if Applicable)
Click to expand log
The text was updated successfully, but these errors were encountered: