summaryrefslogtreecommitdiff
path: root/numpy/distutils/fcompiler
Commit message (Collapse)AuthorAgeFilesLines
* DOC: Comment all O1s [ci skip]Eric Larson2015-12-281-2/+2
|
* FIX: Fix MKL for LinuxEric Larson2015-12-281-2/+2
|
* 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: do not build exclusively for SSE4.2 processorsChristoph Gohlke2015-10-091-1/+1
|
* BLD: mingwpy fixescarlkl2015-09-241-6/+7
|
* MSVCCompiler overwrite 'lib' and 'include' environment variables. ThisDmitry Zagorny2015-09-152-16/+15
| | | | | | | | | behavior affect at least python 3.5 and SciPy build and build failed. During initialization <python>.distutils.MSVCCompiler replace Intel environment('include' and 'lib' paths). This fix decorate 'initialize' function in MSVCCompiler and extend 'lib' and 'include' environment variables. Changed compilation keys: generate optimized code specialized for Intel processors with SSE4.2 support.
* BUG: fix typo which fused two compile flags on Windows for GFortran.Ralf Gommers2015-08-201-1/+1
| | | | Reported in gh-6095.
* BUG: fix 32-bit arch flag for Intel Fortran compiler.Ralf Gommers2015-08-201-1/+1
| | | | See https://software.intel.com/en-us/node/524904. Reported in gh-6095.
* Merge pull request #5597 from zerothi/ENH-distutilsCharles Harris2015-04-243-0/+19
|\ | | | | BLD, ENH: Reading of extra flags from site.cfg to extend flexibility
| * BUG: rpath was not implemented for numpy.distutils.fcompilerNick Papior Andersen2015-02-273-0/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This bug-fix only applies for non gnu-compilers. The fortran compilers in numpy inherited the Ccompier class which had the runtime library directories NotImplemented. Hence the compilers need to define their own runtime library path. I have added that information to the intel/pgi/sun compilers. The rest are either already implemented or I do not know them. I have tested the bug-fix with intel compilers of numpy AND the subsequent installation of scipy (which relies on the fortran compilers). Hence this bug will only occur when linking with the fortran compilers.
* | 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
|/
* DEV: Replace deprecated options for ifort.Åsmund Hjulstad2015-02-101-1/+1
| | | | | The /Qlowercase and /us options has been deprecated in the Intel Visual Fortran Compiler since at least version 2013. Replace with /names:lowercase and /assume:underscore.
* 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.
* BLD: remove "-Wl,-framework,Python" from linker flags for Intel compiler.Ralf Gommers2014-04-211-1/+1
| | | | | | | | | The "-Wl,-undefined,dynamic_lookup" flag is enough to make things work with OS X bundles. On the mailing list an issue was reported with Anaconda (non-framework build) where f2py was picking up the system framework Python instead of the Anaconda one. Thanks to Robert Kern for explaining how to fix this.
* BUG: ifort has issues with optimization flag /O2cgohlke2014-04-081-1/+1
| | | Fixes scipy test failures.
* Revert "Merge pull request #4421 from meltingwax/meltingwax/4382"Daniel da Silva2014-03-051-6/+4
| | | | Caused SciPy tests to fail when built with this NumPy.
* BUG: Fix support for builds in dirs with whitespaceDaniel da Silva2014-03-051-4/+6
| | | | | | Add escaping and quoting of dirs and enabled POSIX support in lexer. Closes #4382.
* 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
* Add '.FOR' to src_extensionsleaz2014-01-051-1/+1
| | | The uppercase source extension '.FOR' is also commonly used.
* Allow checking two or more fortran compilers instead of one.Andrew Stromnov2013-11-011-4/+5
|
* STY: Giant comma spacing fixup.Charles Harris2013-08-1814-107/+107
| | | | | | | 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.
* MAINT: Apply 2to3 idioms fixer.Charles Harris2013-05-021-2/+1
| | | | | | | | | | | | | | | | | | | The idioms fixer makes the following replacements. 1) int <- bool 2) comparison or identity of types <- isinstance 3) a.sort() <- sorted(a) There were two problems that needed to be dealt with after the application of the fixer. First, the replacement of comparison or identity of types by isinstance was not always correct. The isinstance function returns true for subtypes whereas many of the places where the fixer made a substitution needed to check for exact type equality. Second, the sorted function was applied to arrays, but because it treats them as iterators and constructs a sorted list from the result, that is the wrong thing to do. Closes #3062.
* ENH: remove obsolete ifort flags, ensure generated binaries work everywhere.David Cournapeau2013-04-231-14/+5
|
* MAINT: Fixup more dictionary fixer fixes.Charles Harris2013-04-071-2/+2
| | | | | | Most of these are places where an iterator will work as well as a list, but two fix places where `iterkeys` was introduced which is a bug.
* 2to3: apply `dict` fixer.Charles Harris2013-04-061-2/+2
| | | | | | | | | | | | | | | In Python3 `dict.items()`, `dict.keys()`, and `dict.values()` are iterators. This causes problems when a list is needed so the 2to3 fixer explicitly constructs a list when is finds on of those functions. However, that is usually not necessary, so a lot of the work here has been cleaning up those places where the fix is not needed. The big exception to that is the `numpy/f2py/crackfortran.py` file. The code there makes extensive use of loops that modify the contents of the dictionary being looped through, which raises an error. That together with the obscurity of the code in that file made it safest to let the `dict` fixer do its worst. Closes #3050.
* 2to3: Apply `print` fixer.Charles Harris2013-04-0616-19/+19
| | | | | | | 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-2816-16/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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: Remove xreadlines and replace f.readlines() by f where valid.Charles Harris2013-03-052-2/+2
| | | | | | | | | | An open file `f` has been an iterator since python2.3 and `f.xreadlines()` is no longer needed, so replace it with `f`. Also replace `f.readlines()` with `f` where an iterator will do. The replacement of `f.readlines()` is not critical because it is a list in both python2 and python3, but the code is a bit cleaner. Closes #3093
* 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-0116-1/+26
| | | | | | | | 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.
* Style: use 4 spaces per indentation level as per PEP8cgohlke2012-09-161-26/+26
|
* Fix whitespace formattingcgohlke2012-09-161-1/+1
| | | Use spaces instead of tabs
* MAINT: update Intel Fortran compiler flags for the 21st century.Ralf Gommers2012-09-091-55/+16
| | | | | | Thanks to Intel for this contribution. Note that there's also an MKL application note which recommends these flags: http://software.intel.com/en-us/articles/numpyscipy-with-intel-mkl
* prefer gfortran over g77 and vendor compilers on OS X and LinuxAron Ahmadia2012-07-171-4/+4
|
* prefer gfortran (g95) over vendor compilers, g77 and g95 on OSX and Linux. ahmadia2012-06-281-8/+8
| | | Retain preference for g77 on Windows and vendor compilers on other platforms.
* BUG: '-framework Python' is not needed and can interfere.Robert Kern2012-05-311-1/+1
|
* BLD: Avoid repeatedly testing for the Fortran compiler when it is missingMark Wiebe2012-02-191-0/+8
|
* MAINT: update version match regexp for IBM AIX Fortran compilers.Carlos Valiente2011-12-051-1/+1
| | | | | | | | | | | The patched version correctly matches the output of ``xlf -qversion`` on my AIX platform: $ uname -a AIX c1t0101 3 5 00CF49B14C00 $ xlf -qversion IBM XL Fortran for AIX, V12.1 Version: 12.01.0000.0000 $
* ENH: Add 'pgfortran' as a valid compiler in the Portland Grouptim cera2011-10-231-10/+10
| | | | suite of fortran compilers. Adjust the version string command.
* ENH: Introduce new options extra_f77_compile_args and extra_f90_compile_args toPearu Peterson2011-08-201-1/+14
| | | | | | Configuration.add_extension. Configuration.add_library, and Extension. These options allow specifying extra compile options for compiling Fortran sources within a setup.py file.
View Lorry Controller Status