Skip to content

Static link executables attached to release #780

@everythingfunctional

Description

@everythingfunctional

I just encountered a situation where fpm stopped working in the MacOS CI on one of my projects. Apparently GitHub recently changed the MacOS CI environment to no longer include one of the older gfortran run-time libraries that the fpm release is apparently dynamically linked against. We should probably make it standard practice that the fpm executable available from the release page is fully self-contained (e.g. fully static linked) to prevent things like this from breaking.

On a side note, it may also be desirable for the fpm action to test that fpm works correctly once installed. I'll open an issue on that repo to track it there.

FYI, the immediate workaround is to add brew install gcc@9 to any MacOS CI scripts that need to execute fpm.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions