I'm here... i am rolling back now and will post my results...
e
On Mon, May 19, 2008 at 9:22 AM, rex <[EMAIL PROTECTED]> wrote:
>> Next step is to try icc instead of gcc, and if that works, try
>> the latest MKL (10.0.3.020).
>
> OK, either I've got a corrupted copy of MKL 10.0.3.020, or it has
>
> Next step is to try icc instead of gcc, and if that works, try
> the latest MKL (10.0.3.020).
OK, either I've got a corrupted copy of MKL 10.0.3.020, or it has
a problem. Building with icc & MKL 10.0.1.014 works.
Erik, are you reading this? If so, roll back to MKL 10.0.014 and it
should work,
> Please follow exactly my instruction, otherwise, we cannot compare what
> we are doing: use exactly the same site.cfg as me.
OK, I used the same MKL version you did (10.0.1.014), the same
site.cfg, and set .bashrc to do:
source /opt/intel/mkl/10.0.1.014/tools/environment/mklvars32.sh
and comp
rex wrote:
>
> I always remove the build directory (if I forget the much faster
> compilation reminds me). Do you mean remove the installed numpy?
>
Yes.
> Did that, built numpy again, and it fails numpy.test() exactly as before.
>
> I changed site.cfg to:
>
> [mkl]
> library_dirs = /opt/intel
> No, they heavily changed how to link against mkl in 10. There is a whole
> chapter about it in the releases notes.
Yes, I read it, but it appears to me that the new layer libraries
are an option, and that the legacy link format still works. From
chapter 3:
"Pure layered libraries give more fle
