Re: [julia-users] obscure error in Julia 0.3.3

2014-12-22 Thread Milan Bouchet-Valat
Le lundi 22 décembre 2014 à 07:23 -0800, Andrei Berceanu a écrit : Hi guys, The issue persists on my arch box, and converting the matrix from sparse to dense takes up too much memory. Are there any temporary workarounds, while waiting for the upstream fix? The bug seems to be in Arch rather

Re: [julia-users] obscure error in Julia 0.3.3

2014-12-17 Thread Tony Kelman
Might be a good idea to package OpenBLAS for Arch, if you can't find an existing PKGBUILD. On Tuesday, December 16, 2014 2:22:10 PM UTC-8, Milan Bouchet-Valat wrote: Le mardi 16 décembre 2014 à 13:27 -0800, Elliot Saba a écrit : I think the problem here is that we might be using something

Re: [julia-users] obscure error in Julia 0.3.3

2014-12-17 Thread Valentin Churavy
There is an AUR pkgbuild, but since Julia is in community we can not depend on that. But yeah the system BLAS seems to be at fault. I added the Arch maintainer of Julia to the conversation. @Alexander. There seems to be an issue with the BLAS implementation for Julia. Would it be possible to

Re: [julia-users] obscure error in Julia 0.3.3

2014-12-16 Thread Andrei Berceanu
Ok, so here is the output from versioninfo() from inside the Julia REPL: *Julia Version 0.3.3Commit b24213b (2014-11-23 20:19 UTC)Platform Info: System: Linux (x86_64-unknown-linux-gnu) CPU: Intel(R) Xeon(R) CPU X5650 @ 2.67GHz WORD_SIZE: 64 BLAS: libblas LAPACK:

Re: [julia-users] obscure error in Julia 0.3.3

2014-12-16 Thread Andrei Berceanu
I now have a more accurate description of when the error happens. If I try to solve the following linear system *A* *1681x1681 sparse matrix with 8321 Complex{Float64} entries: [1 ,1] = -10.95+0.001im [2 ,1] = 0.415415-0.909632im [42 ,1] =

Re: [julia-users] obscure error in Julia 0.3.3

2014-12-16 Thread Valentin Churavy
So your system setup is exactly the same (except me running on CPU: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz) and I can conform that the following code A = sparse([rand() + rand() * im for i in 1:100, j in 1:100]) B = [rand() + rand() * im for i in 1:100] A\B leads to the following error:

Re: [julia-users] obscure error in Julia 0.3.3

2014-12-16 Thread Valentin Churavy
So building it from the PKGBUILD leads to the same error. I am now building it with the same make options from the tar.gz on the Julia download page. Andrei we probably have to build other parts that interact with suitesparse from source instead of using the Arch ones. But if the problem

Re: [julia-users] obscure error in Julia 0.3.3

2014-12-16 Thread Valentin Churavy
So using make \ USE_SYSTEM_LLVM=0 \ USE_SYSTEM_LIBUNWIND=1 \ USE_SYSTEM_READLINE=0 \ USE_SYSTEM_PCRE=1 \ USE_SYSTEM_LIBM=1 \ USE_SYSTEM_OPENLIBM=0 \ USE_SYSTEM_OPENSPECFUN=0 \ USE_SYSTEM_BLAS=1 \ USE_SYSTEM_LAPACK=1 \ USE_SYSTEM_FFTW=1 \

Re: [julia-users] obscure error in Julia 0.3.3

2014-12-16 Thread Valentin Churavy
Ok setting USE_SYSTEM_BLAS=0 \ USE_SYSTEM_LAPACK=0 \ USE_SYSTEM_SUITESPARSE=0 \ Make the problem go away. So it is the interaction between the system blas/lapack and the built suitesparese. Are there any patches that julia carries over suitesparse 4.4.1? On Tuesday, 16 December 2014 17:28:28

Re: [julia-users] obscure error in Julia 0.3.3

2014-12-16 Thread Valentin Churavy
So I narrowed it down to combining the system's blas with Julia's suitesparse. In the tests I made laplack has no influence. Should I file an issue against Julia or with the Archlinux package? What are the Fedora packages bundling? USE_SYSTEM_BLAS=1 \ USE_SYSTEM_SUITESPARSE=0 \ On Tuesday,

Re: [julia-users] obscure error in Julia 0.3.3

2014-12-16 Thread Elliot Saba
I think the problem here is that we might be using something that requires a certain version of BLAS or LAPACK, or possibly a patched LAPACK or something. We get a patched LAPACK when we build OpenBLAS. I've directly included Andreas in this reply, as he's the kind of guy that would have a good

[julia-users] obscure error in Julia 0.3.3

2014-12-15 Thread Andrei Berceanu
Hi all, I recently upgraded to Julia Version 0.3.3 on my Arch Linux box and sometimes get this strange error, followed by a kernel crash - what gives? julia: symbol lookup error: /usr/bin/../lib/julia/libcholmod.so: undefined symbol: zpotrf_ //A

Re: [julia-users] obscure error in Julia 0.3.3

2014-12-15 Thread João Felipe Santos
You may need to clean and rebuild the dependencies as well as core Julia. On Dec 15, 2014, at 12:08 PM, Andrei Berceanu andreiberce...@gmail.com wrote: Hi all, I recently upgraded to Julia Version 0.3.3 on my Arch Linux box and sometimes get this strange error, followed by a kernel

Re: [julia-users] obscure error in Julia 0.3.3

2014-12-15 Thread Elliot Saba
Ah, yes. If you haven't, try a `make -C deps distclean arpack-julia distclean-openblas distclean-suitesparse`, then `make cleanall` and finally `make`. -E On Mon, Dec 15, 2014 at 9:11 AM, João Felipe Santos joao@gmail.com wrote: You may need to clean and rebuild the dependencies as well as

Re: [julia-users] obscure error in Julia 0.3.3

2014-12-15 Thread Andrei Ciprian Berceanu
Where do i need to type all this? I must mention that I did not compile Julia from source, but used my distribution's (arch linux) package manager (pacman). On December 15, 2014 6:15:09 PM CET, Elliot Saba staticfl...@gmail.com wrote: Ah, yes. If you haven't, try a `make -C deps distclean

Re: [julia-users] obscure error in Julia 0.3.3

2014-12-15 Thread Valentin Churavy
A fellow archuser here. Under which circumstances does the error occur? Eg. what code are you executing? And what does pacman -Qi julia blas lapack output On Monday, 15 December 2014 19:14:22 UTC+1, Andrei Berceanu wrote: Where do i need to type all this? I must mention that I did not

Re: [julia-users] obscure error in Julia 0.3.3

2014-12-15 Thread Elliot Saba
If you didn't compile, then ignore my second message and Joao's. Running `versioninfo()` from the julia prompt will give some information about your system configuration, and Valentin's question, (running `pacman -Qi julia blas lapack`) will be helpful to know the answer to as well. -E On Mon,