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
On Sun, 2008-05-18 at 12:14 -0700, rex wrote:
>
> The last relevant MKL library name change I'm aware of occurred
> when MKL 9.X was released in 2006:
>
No, they heavily changed how to link against mkl in 10. There is a whole
chapter about it in the releases notes.
> ldd shows MKL was linked:
>
David, how do these environment variables compare with yours? Are you sure
MKL is being used?
Adjusted for your local path, what does the ldd command below show?
ldd /usr/local/lib/python2.5/site-packages/numpy/linalg/lapack_lite.so
linux-gate.so.1 => (0xe000)
libmkl_lapack.so => /opt
David wrote:
> I have not tried with icc, but the following works for me with the
> last mkl (I have only tried numpy).
>
> [mkl]
> library_dirs = /home/david/intel/mkl/10.0.1.014/lib/32
> lapack_libs = mkl_lapack
> mkl_libs = mkl, guide
>
> (of course, adapt the library_dirs accordingly). All test
On Sun, May 18, 2008 at 7:13 PM, rex <[EMAIL PROTECTED]> wrote:
>
>> I am trying to build numpy with intel icc and mkl. I don't understand
>> a lot of what I am doing.
>
> Me, too. I have built it with icc & MKL several times in the past,
> but cannot build the numpy svn with MKL now. I can build
> I am trying to build numpy with intel icc and mkl. I don't understand
> a lot of what I am doing.
Me, too. I have built it with icc & MKL several times in the past,
but cannot build the numpy svn with MKL now. I can build it with
icc and no MKL, and it passes all the tests with no errors.
I
I am trying to build numpy with intel icc and mkl. I don't understand
a lot of what I am doing. I have followed the the suggestions of what
to add/change in site.cfg intelccompiler.py and system_info.py from
several different posts or google searches. i am not sure i have done
any of this right.
11 matches
Mail list logo
