summaryrefslogtreecommitdiff
path: root/numpy/distutils/fcompiler/gnu.py
Commit message (Collapse)AuthorAgeFilesLines
* Revert "Merge pull request #5614 from charris/cleanup-gh-5587"Charles Harris2015-10-201-22/+10
| | | | | | | | | Revert mingwpy modifications to distutils. They are causing problems for non-windows builds and it is better to wait until mingypy is further along. This reverts commit 96abd32de241864ee97f30357234cbc9a96c43ae, reversing changes made to 06af9918f6bf03b8d818ec834f9fb48db57d1489.
* Revert "Merge pull request #6354 from mingwpy/mingwpy"Charles Harris2015-10-201-7/+6
| | | | | | | | | Revert mingwpy modifications to distutils. They are causing problems for non-windows builds and it is better to wait until mingypy is further along. This reverts commit cda64938eb150b1af6677db4754da3be5fd7e483, reversing changes made to 8cb3ec6ab804f594daf553e53e7cf7478656bebd.
* BLD: mingwpy fixescarlkl2015-09-241-6/+7
|
* BUG: fix typo which fused two compile flags on Windows for GFortran.Ralf Gommers2015-08-201-1/+1
| | | | Reported in gh-6095.
* BLD: distutils: more robust gfortran version checking. Closes gh-5768.Ralf Gommers2015-04-191-14/+33
|
* Merge pull request #5644 from rgommers/fix-gfortran-version-checkCharles Harris2015-03-081-0/+4
|\ | | | | BLD: fix gfortran version check, and make distutils.test() work
| * MAINT: distutils: fix gfortran version check when gfortran emits warnings.Ralf Gommers2015-03-071-0/+4
| |
* | STY: Some style cleanups in distutils.Charles Harris2015-02-271-44/+22
| | | | | | | | | | | | Break long lines. Spaces around operators. Remove dead code.
* | BLD: Add mingw-w64 support for the mingw64static option.carlkl2015-02-271-10/+21
|/
* Removed NotImplementedError for MinGW-w64Juan Luis Cano Rodríguez2014-12-291-1/+1
| | | Closes #3405
* BLD: Change Fortran version flag and string checkRyan Nelson2014-12-011-17/+18
| | | | | | | The version check flag for GnuFCompiler and Gnu95FCompiler were changed from `--version` to `-dumpversion`. This simplifies the gnu_version_match code for gfortran, and makes it possible to drop much of the check code for g77 as well. This fix addresses issue #5315 and #5321.
* Merge pull request #4996 from fdiary/gfortran-rpathJulian Taylor2014-08-261-0/+3
|\ | | | | | | support rpath for GNU Fortran compiler.
| * BLD: support rpath for GNU Fortran compiler.Kazuhiko Shiozaki2014-08-261-0/+3
| |
* | BLD: add debug information to gfortran buildsJulian Taylor2014-08-241-4/+5
|/ | | | Similar to C builds which always have debug info.
* Detect vendor versions of GNU CompilersAron Ahmadia2014-02-041-3/+3
| | | | | | | | Cray and other HPC vendors provide patched versions of the GNU compilers with modified version strings. Use re.search instead of re.match in the version detection scripts to account for modified version strings. Ref: https://github.com/numpy/numpy/issues/4259
* STY: Giant comma spacing fixup.Charles Harris2013-08-181-1/+1
| | | | | | | Run the 2to3 ws_comma fixer on *.py files. Some lines are now too long and will need to be broken at some point. OTOH, some lines were already too long and need to be broken at some point. Now seems as good a time as any to do this with open PRs at a minimum.
* BUG: Handle a version string from a custom-built mingw64.mwtoews2013-05-291-1/+1
| | | | | | | | The custom build compiler "GNU Fortran (rubenvb-4.8.0) 4.8.0" was incorrectly parsed as version '-4.8.0' and the flag "-mno-cygwin" was added to the compilation. See http://cens.ioc.ee/pipermail/f2py-users/2010-October/002092.html.
* 2to3: Apply `print` fixer.Charles Harris2013-04-061-1/+1
| | | | | | | Add `print_function` to all `from __future__ import ...` statements and use the python3 print function syntax everywhere. Closes #3078.
* 2to3: Use absolute imports.Charles Harris2013-03-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The new import `absolute_import` is added the `from __future__ import` statement and The 2to3 `import` fixer is run to make the imports compatible. There are several things that need to be dealt with to make this work. 1) Files meant to be run as scripts run in a different environment than files imported as part of a package, and so changes to those files need to be skipped. The affected script files are: * all setup.py files * numpy/core/code_generators/generate_umath.py * numpy/core/code_generators/generate_numpy_api.py * numpy/core/code_generators/generate_ufunc_api.py 2) Some imported modules are not available as they are created during the build process and consequently 2to3 is unable to handle them correctly. Files that import those modules need a bit of extra work. The affected files are: * core/__init__.py, * core/numeric.py, * core/_internal.py, * core/arrayprint.py, * core/fromnumeric.py, * numpy/__init__.py, * lib/npyio.py, * lib/function_base.py, * fft/fftpack.py, * random/__init__.py Closes #3172
* 2to3:DEP: Remove interactive setup and gnu compiler configuration.Charles Harris2013-03-051-2/+2
| | | | | | | | | | | | | | | | | | | | | | These havn't been deprecated, but I think few have heard of them, much less used them. Before this change, running setup.py without any arguments would result in interactive help. This patch removes that interactive help and lets setup print its usual list of commands and options. All the script uses of the numpy/distutils/fcompiler compilers look quite broken to me, but I have tried to maintain compatibility with the earlier version of gnu.py after the removal of `raw_input`. These removals solve an incompatibility between Python3 and Python2. The current interactive setup help uses `raw_input`, which has been removed in python3 and replaced by `input`. However, python2 already has an `input` that has different semantics. Rather than deal with this, I think it simpler to keep both `raw_input` and `input` out of numpy. Closes #3063 Closes #3079
* 2to3: Put `from __future__ import division in every python file.Charles Harris2013-03-011-0/+2
| | | | | | | | This should be harmless, as we already are division clean. However, placement of this import takes some care. In the future a script can be used to append new features without worry, at least until such time as it exceeds a single line. Having that ability will make it easier to deal with absolute imports and printing updates.
* Fix whitespace formattingcgohlke2012-09-161-1/+1
| | | Use spaces instead of tabs
* BUG: fix issue with incorrect Fortran arch flags. Closes #1399.rgommers2010-11-071-1/+31
| | | | | The basic idea here is to compare arch flags the Fortran compiler supports with the ones the C compiler receives, and throw out any superfluous ones.
* BUG: on Windows the sysconfig module does not contain CFLAGS info.rgommers2010-10-171-1/+4
|
* UPDATE: gcc-4 series do not support -mno-cygwin option.Pearu Peterson2010-10-161-7/+11
|
* BF - get fortran arch flags from C arch flags if availableMatthew Brett2010-10-161-25/+11
|
* BUG: Enable compiling Fortran code on OS X for ppc64 arch.rgommers2010-06-021-8/+8
| | | | Thanks to David Warde-Farley. Fixes #1399.
* BUG: Fix #1376, indentation problem.Travis Oliphant2010-02-041-2/+2
|
* BUG: fix 1087, thanks to Leek for the fix.David Cournapeau2009-12-101-16/+17
|
* Py3k: Fix comparison when version is None.David Cournapeau2009-12-031-2/+5
|
* BUG: fix mixed tab/space indentation.David Cournapeau2009-12-031-10/+10
|
* Fix print statements in fcompiler for python3.David Cournapeau2009-12-031-3/+3
|
* BUG: fix the detection of architectures on OS X.Robert Kern2009-09-021-4/+3
|
* Use subprocess instead of exec_command to detect universal archs of gfortran.David Cournapeau2009-08-271-1/+4
|
* Update mingw-w64 support for gfortran.David Cournapeau2009-08-261-1/+2
| | | | | Gfortran does not append a leading underscore anymore, so the -fno-leading-underscore is not necessary anymore.
* Fix missing variable def in gfortran tool.David Cournapeau2009-06-301-0/+2
|
* Update gfortran support on win64David Cournapeau2009-06-301-3/+23
| | | | | | | We don't link the gfortran runtime when built with MS compilers: there are some incompatibilities between libgfortran and dependent libraries (mingwex, etc..) and the MS C runtime. Instead, we will implement the needed function from libgfortran and compile it with MS compiler, with the MS C runtime.
* Add x86_64 arch flag if gfortran supports it.David Cournapeau2009-04-201-1/+1
|
* Make _can_target a function.David Cournapeau2009-04-201-17/+14
|
* Do not detect universal flags on platform != darwin.David Cournapeau2009-03-281-0/+2
|
* BUG: Fix goftran universal flags settings (#1067).David Cournapeau2009-03-281-35/+36
| | | | | | | | Arch flags were detected and set for both linkers and compiler. Since they both used the compiler_f90 as the underlying command, arch flags were added twice to the compiler command for universal detection, which rendered the verbose output of gfortran useless.
* Trust user's specification of MACOSX_DEPLOYMENT_TARGET [patch by BrianStefan van der Walt2009-02-121-14/+22
| | | | Granger].
* ran reindentJarrod Millman2008-12-311-21/+21
|
* Add mingw32 and mingwex libraries as runtime libraries for extensions which ↵David Cournapeau2008-12-161-0/+7
| | | | use fortran and are built with gfortran+MS compiler.
* Fix overriding of library_dirs.David Cournapeau2008-12-161-1/+1
|
* Add target specific lib dir for gfortran on windows when msvc is the C compiler.David Cournapeau2008-12-161-0/+15
|
* Fix get_target.David Cournapeau2008-12-161-1/+1
|
* Add a function to get configured target for gfortran.David Cournapeau2008-12-161-0/+11
|
* BUG: Do not harcode fortran runtime when copying it on windows. Should fix #969.David Cournapeau2008-12-161-2/+2
|
* Remove cpu/arch specific optimization flags for GNU fortran compilers: they ↵David Cournapeau2008-11-061-97/+1
| | | | are too fragile, and are more likely not that useful anyway.
View Lorry Controller Status