8000 numpy 1.10 appears to break setting the fortran compiler when building scipy · Issue #6566 · numpy/numpy · GitHub
[go: up one dir, main page]
Skip to content

numpy 1.10 appears to break setting the fortran compiler when building scipy #6566

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.

Sign up for GitHub

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

Jump to bottom
Closed
opoplawski opened this issue Oct 26, 2015 · 3 comments
Closed

numpy 1.10 appears to break setting the fortran compiler when building scipy #6566

opoplawski opened this issue Oct 26, 2015 · 3 comments
Labels
50 - Duplicate

Comments

@opoplawski
Copy link

After moving to numpy 1.10.0 b2 in Fedora rawhide, we're seeing bad gfortran flags when building scipy:

Fortran f77 compiler: /usr/bin/gfortran -Wall -g -ffixed-form -fno-second-underscore -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m32 -march=i686 -mtune=atom -fasynchronous-unwind-tables -fPIC -O2 -march=x86-64 -DMS_WIN64 -mtune=generic -msse2
Fortran f90 compiler: /usr/bin/gfortran -Wall -g -fno-second-underscore -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m32 -march=i686 -mtune=atom -fasynchronous-unwind-tables -fPIC -O2 -march=x86-64 -DMS_WIN64 -mtune=generic -msse2
Fortran fix compiler: /usr/bin/gfortran -Wall -g -ffixed-form -fno-second-underscore -Wall -g -fno-second-underscore -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -m32 -march=i686 -mtune=atom -fasynchronous-unwind-tables -fPIC -O2 -march=x86-64 -DMS_WIN64 -mtune=generic -msse2

It appears to be tacking on the "-march=x86-64 -DMS_WIN64 -mtune=generic -msse2" options from the mingw settings to the fortran compiler flags.
@pv
Copy link
Member
pv commented Oct 26, 2015

Duplicate of gh-6495?

@pv
Copy link
Member
pv commented Oct 26, 2015

IOW, best to wait for 1.10.2

@opoplawski
Copy link
Author

Yes. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
50 - Duplicate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pv @opoplawski
0