Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A lot of spkgs check for fortran even if they don't need it #3002

Closed
dfdeshom opened this issue Apr 22, 2008 · 1 comment
Closed

A lot of spkgs check for fortran even if they don't need it #3002

dfdeshom opened this issue Apr 22, 2008 · 1 comment

Comments

@dfdeshom
Copy link

A lot of configure scripts seem to check for
fortran, even if they don't use it. It appears the relevant
environment variables are F77 and FFLAGS. Anyway, the variable
SAGE_FORTRAN seems to be honored fine for the packages that actually
need fortran.

Component: packages: standard

Issue created by migration from https://trac.sagemath.org/ticket/3002

@sagetrac-mabshoff
Copy link
Mannequin

sagetrac-mabshoff mannequin commented Apr 22, 2008

comment:1

This is not the case and if we don't use an F77 compiler we shouldn't use the F77 env variable. The fact that a lot of them check for a Fortran compiler and don't use them is also something that doesn't matter since the configure process will not fail. So, the whole ticket is clearly "won't fix" to me.

Thoughts?

Cheers,

Michael

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants