Summary: | dev-python/numpy-1.0.1-r1 doesn't respect CFLAGS | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | James <James> |
Component: | New packages | Assignee: | Sébastien Fabbro (RETIRED) <bicatali> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | python |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Output of emerge info |
Description
James
2007-03-04 10:57:59 UTC
Created attachment 112040 [details]
Output of emerge info
After editing the following file: /usr/lib/python2.4/site-packages/numpy/distutils/fcompiler/gnu.py with this diff --- gnu.py.old 2007-03-04 11:08:43.000000000 +0000 +++ gnu.py 2007-03-04 11:13:41.000000000 +0000 @@ -192,7 +192,7 @@ march_opt = '-march=athlon-mp' # there's also: athlon-tbird, athlon-4, athlon-xp elif cpu.is_Nocona(): - march_opt = '-march=nocona' + march_opt = '-march=pentium4' elif cpu.is_Prescott(): march_opt = '-march=prescott' elif cpu.is_PentiumIV(): My program works again, and the -march=pentium4 is used. I conclude therefore, that the nocona cpu.is_Nocona() function is wrong. I suggest maybe a better fix would be to file: /usr/lib/python2.4/site-packages/numpy/distutils/cpuinfo.py As nocona enables sse3 instructions for nocona, we should do a check for sse3 in the _is_Nocona test routine. --- cpuinfo.py.old 2007-03-04 11:26:20.000000000 +0000 +++ cpuinfo.py 2007-03-04 11:25:14.000000000 +0000 @@ -185,7 +185,7 @@ return self.is_PentiumIV() and self.has_sse3() def _is_Nocona(self): - return self.is_PentiumIV() and self.is_64bit() + return self.is_PentiumIV() and self.is_64bit() and self.has_sse3() def _is_Itanium(self): return re.match(r'.*?Itanium\b', Which ebuild is this about? Definitely NOT gcc. Ah! Sorry, if mentioned gfortran, and that is contained in gcc, so I thought it was gcc. It is actually: dev-python/numpy-1.0.1-r1 Thanks. bicatali: please take care offensichtlich this and set either yourself or the science herd as maintainer. Thanks for reporting. Should be fixed now with an upstream patch, please re-open if it persists. |