git pull
verified that ARM.inc was updated with USE_BLAS64=0
Same error message : ErrorException("BLAS and LAPACK are compiled with
32-bit integer support, but Julia expects 64-bit integers. Please build
Julia with USE_BLAS64=0.")
Unit still compiling.
On Saturday, November 29, 2014 1:03:32 AM UTC-7, Viral Shah wrote:
>
> I added USE_BLAS64=0 to ARM.inc. Could you git pull and try again?
>
> -viral
>
>
>
> > On 29-Nov-2014, at 1:01 pm, Airhead Bit <[email protected]
> <javascript:>> wrote:
> >
> > Yes, followed the directions made a Make.user added the include ARM.inc
> if I had not I don't think the compile would have completed, no x86 stuff
> on the Radxa box where I compiled it.
> > No, I don't think an ARMv8 would even run ARM7 code, not sure.
> > Radxa Rock Pro is ARM7 hfp with an ARM9 (quad core ARM7) 2GB memory, 8GB
> Flash, desktop box, nice for working with Android.
> >
> > Should I add USE_BLAS64=0 to the Make.user and re-compile?
> > Is there a way to have make testall load juliadebug test/all?
> >
> >
> >
> > On Friday, November 28, 2014 11:18:39 AM UTC-7, Airhead Bit wrote:
> > Just finished compiling one Error:
> > Warning: error initializing module LinAlg:
> > ErrorException("BLAS and LAPACK are compiled with 32-bit integer
> support, but Julia expects 64-bit integers. Please build Julia with
> USE_BLAS64=0.")
> > exports.jl
> >
> > Julia works at the prompt but: TOP shows 400% CPU...
> >
> > root@radxa:~/julia# make testall
> > JULIA test/all
> > Master process (id 1) could not connect within 60.0 seconds.
> > exiting.
> > Master process (id 1) could not connect within 60.0 seconds.
> > exiting.
> > Master process (id 1) could not connect within 60.0 seconds.
> > exiting.
> > Worker 5 terminated.
> > Worker 4 terminated.Worker 2 terminated.
> >
> > Eventually I was left with two Julia process's that each took 198.n%
> until I killed the terminal
> > I'm going to build a clean system and build adding USE_BLAS64=0 in the
> Make.user file.
> >
> > Any other ideas for a build?
> > Any ideas on how to tell what is sucking all the CPU?
> >
> >
>
>
