[Numpy-tickets] [NumPy] #520: intel compiler package uses arch specific flags in get_flags_linker_so that can't be overridden
NumPy
numpy-tickets@scipy....
Mon May 14 15:43:14 CDT 2007
#520: intel compiler package uses arch specific flags in get_flags_linker_so that
can't be overridden
---------------------+------------------------------------------------------
Reporter: mbeachy | Owner: somebody
Type: defect | Status: new
Priority: normal | Milestone:
Component: Other | Version: none
Severity: normal | Keywords:
---------------------+------------------------------------------------------
I've been trying to set up configuration files to standardize a local 1.02
numpy installation and have run into a problem with the intel compiler
package. If I try
`python setup.py config_fc --fcompiler=intel build_ext`
(from the top level numpy-1.0.2 directory) I get the following failures
(with ifort 8.1):
{{{
ifort: Command line warning: extension 'M' not supported ignored in option
'-x'
ifort: Command line error: Unrecognized keyword 'SSE2' for option '-arch'
ifort: Command line warning: extension 'M' not supported ignored in option
'-x'
ifort: Command line error: Unrecognized keyword 'SSE2' for option '-arch'
}}}
I assumed that the 'noarch' option to the config_fc command would get me
around this, but it does not. This seems to be because the
get_flags_linker_so method in the
numpy.distutils.fcompiler.intel.IntelFCompiler class always extends the
options with the result of self.get_flags_arch(). Removing that call fixes
the problem.
I don't think that having architecture specific flags in the shared linker
options even matters, does it? It would be nice if we could just get rid
of the self.get_flags_arch() call in get_flags_linker_so for the 1.03
release.
--
Ticket URL: <http://projects.scipy.org/scipy/numpy/ticket/520>
NumPy <http://projects.scipy.org/scipy/numpy>
The fundamental package needed for scientific computing with Python.
More information about the Numpy-tickets
mailing list