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

Can't find gfortan on RHEL 6.4 #5768

Closed
ewmoore opened this issue Apr 15, 2015 · 3 comments
Closed

Can't find gfortan on RHEL 6.4 #5768

ewmoore opened this issue Apr 15, 2015 · 3 comments
Assignees
Labels
00 - Bug component: numpy.distutils Priority: high High priority, also add milestones for urgent issues

Comments

@ewmoore
Copy link
Contributor

ewmoore commented Apr 15, 2015

I cannot build Scipy against a current numpy on RHEL 6.4. Running gfortran --version or gfortran -dumpversion both provide the same output:

GNU Fortran (GCC) 4.4.7 20120313 (Red Hat 4.4.7-3)
Copyright (C) 2010 Free Software Foundation, Inc.

GNU Fortran comes with NO WARRANTY, to the extent permitted by law.
You may redistribute copies of GNU Fortran
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING

This has to do with the changes made to how gnu fortran compilers are detected in #5333. Going back to 8a2dd06 works.

This isn't the newest RHEL, but it is still in the full support phase.

@rgommers
Copy link
Member

Hmm, the whole point of using -dumpversion was to remove the need for parsing random version strings. If there's gfortran versions floating around where -dumpversion is an alias for --version we should probably just revert gh-5333.

@rgommers rgommers added 00 - Bug Priority: high High priority, also add milestones for urgent issues component: numpy.distutils labels Apr 16, 2015
@rgommers rgommers self-assigned this Apr 16, 2015
@ewmoore
Copy link
Contributor Author

ewmoore commented Apr 17, 2015

Any version of gfortran from earlier than this gcc commit from Aug 2010 will produce the same output for --version and -dumpversion. So yes, there absolutely are versions where this is true.

There is always the try harder option. Use the new check if -dumpversion produces only a single line of output, otherwise try the old check against the --version output. This ought to keep the cases fixed by #5333 working and allow older versions to still work.

@rgommers
Copy link
Member

Good idea. Done in gh-5774.

juliantaylor added a commit that referenced this issue Apr 19, 2015
BLD: distutils: more robust gfortran version checking.  Closes gh-5768.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
00 - Bug component: numpy.distutils Priority: high High priority, also add milestones for urgent issues
Projects
None yet
Development

No branches or pull requests

2 participants