Skip to content

Conversation

staticfloat
Copy link
Member

On systems where we don't have gfortran installed, there's no reason
to require it, because nowadays we get everything from Yggdrasil anyway.
Simply soldier on and assume that the user wants the latest support
libraries, unless they are trying to build from source.

This is particularly useful on Apple M1 machines, where a native build of gfortran is a bother to install.

@staticfloat staticfloat mentioned this pull request Jan 20, 2021
31 tasks
On systems where we don't have `gfortran` installed, there's no reason
to require it, because nowadays we get everything from Yggdrasil anyway.
Simply soldier on and assume that the user wants the latest support
libraries, unless they are trying to build from source.
@staticfloat staticfloat merged commit 6b91bbb into master Feb 3, 2021
@staticfloat staticfloat deleted the sf/gfortran_be_gone branch February 3, 2021 19:59
ElOceanografo pushed a commit to ElOceanografo/julia that referenced this pull request May 4, 2021
JuliaLang#39338)

On systems where we don't have `gfortran` installed, there's no reason
to require it, because nowadays we get everything from Yggdrasil anyway.
Simply soldier on and assume that the user wants the latest support
libraries, unless they are trying to build from source.
antoine-levitt pushed a commit to antoine-levitt/julia that referenced this pull request May 9, 2021
JuliaLang#39338)

On systems where we don't have `gfortran` installed, there's no reason
to require it, because nowadays we get everything from Yggdrasil anyway.
Simply soldier on and assume that the user wants the latest support
libraries, unless they are trying to build from source.
@fredrikekre
Copy link
Member

@staticfloat should this be backported to 1.6, or should

"11": "libgfortran5",
be patched to allow building with gfortran 12?

@staticfloat
Copy link
Member Author

If possible, backporting to 1.6 is preferred

@fredrikekre fredrikekre added the backport 1.6 Change should be backported to release-1.6 label May 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 1.6 Change should be backported to release-1.6
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants