Re: [julia-users] Julia on ARM Radxa Rock Pro Quad Core

2014-11-30 Thread Airhead Bit
More INFO:
--
julia versioninfo(true)
Julia Version 0.4.0-dev+1876
Commit a0542e7 (2014-11-30 02:13 UTC)
Platform Info:
  System: Linux (arm-linux-gnueabihf)
  CPU: ARMv7 Processor rev 0 (v7l)
  WORD_SIZE: 32
   Linaro 14.04
  uname: Linux 3.0.36+ #14 SMP PREEMPT Tue Aug 26 13:51:06 CST 2014 armv7l 
armv7l
Memory: 2.0 GB (1366.35546875 MB free)
Uptime: 2827.0 sec
Load Avg:  2.22607421875  0.77392578125  0.41015625
ARMv7 Processor rev 0 (v7l):
   speed user nice  sys idle 
 irq
#1  1008 MHz   2372 s  0 s  30710 s 243273 s 51 
s
#2  1008 MHz   2236 s  0 s   3846 s 273905 s  0 
s
#3  1008 MHz   1864 s  0 s   4416 s 271809 s  0 
s
#4  1008 MHz   3116 s  0 s   2180 s 275603 s  0 
s

  BLAS: libopenblas (NO_AFFINITY ARMV7)
  LAPACK: libopenblas
  LIBM: libm
  LLVM: libLLVM-3.5.0
Environment:
  TERM = xterm
  PATH = 
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
  HOME = /root

Package Directory: /root/.julia/v0.4
INFO: Initializing package repository /root/.julia/v0.4
INFO: Cloning METADATA from git://github.com/JuliaLang/METADATA.jl
No packages installed

julia

--

root@radxa:~/julia# cat /proc/cpuinfo
Processor   : ARMv7 Processor rev 0 (v7l)
processor   : 0
BogoMIPS: 3214.95

processor   : 1
BogoMIPS: 3214.95

processor   : 2
BogoMIPS: 3214.95

processor   : 3
BogoMIPS: 3214.95

Features: swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part: 0xc09
CPU revision: 0

Hardware: RK30board
Revision: 
Serial  : 


On Sunday, November 30, 2014 12:36:34 AM UTC-7, Airhead Bit wrote:

 Finished compiling, Lots of warnings, %CPU at 299~310, Used your below 
 test and mine is the same.
 How can we find what is spinning all the CPU cycles?


 https://lh4.googleusercontent.com/-ZtUw4ml2dXc/VHrI7joXJhI/AFs/VGb5yUeYq-8/s1600/htop.JPG


 On Saturday, November 29, 2014 9:17:33 PM UTC-7, Viral Shah wrote:

 However, upon building, it looks ok, and peakflops() which was crashing 
 for me before works fine now. 

 julia Base.LinAlg.BlasInt 
 Int32 

 julia Base.USE_BLAS64 
 false 


 -viral 



  On 30-Nov-2014, at 9:31 am, Viral Shah vi...@mayin.org wrote: 
  
  Interestingly, I get the same error now. I had cleaned out the whole 
 openblas directory before starting the build. 
  
  -viral 
  
  
  
  On 30-Nov-2014, at 6:14 am, Isaiah Norton isaiah...@gmail.com 
 wrote: 
  
  You will probably need to do `make -C deps clean-openblas` first (or 
 just remove the openblas-0.2.12 subdirectory). 
  
  On Sat, Nov 29, 2014 at 7:01 PM, Airhead Bit airhe...@gmail.com 
 wrote: 
  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 airhe...@gmail.com 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 

Re: [julia-users] Julia on ARM Radxa Rock Pro Quad Core

2014-11-29 Thread Viral Shah
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 airhead...@gmail.com 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?
  
 



Re: [julia-users] Julia on ARM Radxa Rock Pro Quad Core

2014-11-29 Thread Airhead Bit
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 airhe...@gmail.com 
 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? 

  



Re: [julia-users] Julia on ARM Radxa Rock Pro Quad Core

2014-11-29 Thread Isaiah Norton
You will probably need to do `make -C deps clean-openblas` first (or just
remove the openblas-0.2.12 subdirectory).

On Sat, Nov 29, 2014 at 7:01 PM, Airhead Bit airhead...@gmail.com wrote:

 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 airhe...@gmail.com 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?
 
 




Re: [julia-users] Julia on ARM Radxa Rock Pro Quad Core

2014-11-29 Thread Airhead Bit
Thanks, I'll try again

On Saturday, November 29, 2014 5:44:18 PM UTC-7, Isaiah wrote:

 You will probably need to do `make -C deps clean-openblas` first (or just 
 remove the openblas-0.2.12 subdirectory).

 On Sat, Nov 29, 2014 at 7:01 PM, Airhead Bit airhe...@gmail.com 
 javascript: wrote:

 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 airhe...@gmail.com 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? 

  




Re: [julia-users] Julia on ARM Radxa Rock Pro Quad Core

2014-11-29 Thread Viral Shah
Interestingly, I get the same error now. I had cleaned out the whole openblas 
directory before starting the build.

-viral



 On 30-Nov-2014, at 6:14 am, Isaiah Norton isaiah.nor...@gmail.com wrote:
 
 You will probably need to do `make -C deps clean-openblas` first (or just 
 remove the openblas-0.2.12 subdirectory).
 
 On Sat, Nov 29, 2014 at 7:01 PM, Airhead Bit airhead...@gmail.com wrote:
 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 airhe...@gmail.com 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? 

  
 
 



Re: [julia-users] Julia on ARM Radxa Rock Pro Quad Core

2014-11-29 Thread Viral Shah
However, upon building, it looks ok, and peakflops() which was crashing for me 
before works fine now.

julia Base.LinAlg.BlasInt
Int32

julia Base.USE_BLAS64
false


-viral



 On 30-Nov-2014, at 9:31 am, Viral Shah vi...@mayin.org wrote:
 
 Interestingly, I get the same error now. I had cleaned out the whole openblas 
 directory before starting the build.
 
 -viral
 
 
 
 On 30-Nov-2014, at 6:14 am, Isaiah Norton isaiah.nor...@gmail.com wrote:
 
 You will probably need to do `make -C deps clean-openblas` first (or just 
 remove the openblas-0.2.12 subdirectory).
 
 On Sat, Nov 29, 2014 at 7:01 PM, Airhead Bit airhead...@gmail.com wrote:
 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 airhe...@gmail.com 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? 
 
 
 
 
 



Re: [julia-users] Julia on ARM Radxa Rock Pro Quad Core

2014-11-29 Thread Viral Shah
Yes, the ARM nomenclature is a huge alphabet soup. This could be handy, I 
suppose:

http://en.wikipedia.org/wiki/List_of_ARM_microarchitectures

-viral



 On 30-Nov-2014, at 1:38 am, Airhead Bit airhead...@gmail.com wrote:
 
 Another Correction:
  The RK3188 features a quad-core ARM Cortex-A9  - The RK3288 is based on the 
 Quad Core Cortex-A17
 The Radxa Rock Pro is a RK3188 Cortex-A9
 It's like ARM has a dice shaker with letters and number and each letter and 
 number has it's own dice shaker, add to the the convoluted information on the 
 internet your head explodes.

 On Saturday, November 29, 2014 12:02:11 PM UTC-7, Airhead Bit wrote:
 Correction: Quad-Core Cortex-A17 is an ARMv7 based product RK3188 - I have no 
 idea where I got ARM9 from
 
 On Saturday, November 29, 2014 12:31:28 AM UTC-7, Airhead Bit 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?
  
 



Re: [julia-users] Julia on ARM Radxa Rock Pro Quad Core

2014-11-29 Thread Airhead Bit
Finished compiling, Lots of warnings, %CPU at 299~310, Used your below test 
and mine is the same.
How can we find what is spinning all the CPU cycles?

https://lh4.googleusercontent.com/-ZtUw4ml2dXc/VHrI7joXJhI/AFs/VGb5yUeYq-8/s1600/htop.JPG


On Saturday, November 29, 2014 9:17:33 PM UTC-7, Viral Shah wrote:

 However, upon building, it looks ok, and peakflops() which was crashing 
 for me before works fine now. 

 julia Base.LinAlg.BlasInt 
 Int32 

 julia Base.USE_BLAS64 
 false 


 -viral 



  On 30-Nov-2014, at 9:31 am, Viral Shah vi...@mayin.org javascript: 
 wrote: 
  
  Interestingly, I get the same error now. I had cleaned out the whole 
 openblas directory before starting the build. 
  
  -viral 
  
  
  
  On 30-Nov-2014, at 6:14 am, Isaiah Norton isaiah...@gmail.com 
 javascript: wrote: 
  
  You will probably need to do `make -C deps clean-openblas` first (or 
 just remove the openblas-0.2.12 subdirectory). 
  
  On Sat, Nov 29, 2014 at 7:01 PM, Airhead Bit airhe...@gmail.com 
 javascript: wrote: 
  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 airhe...@gmail.com 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? 
  
  
  
  
  



Re: [julia-users] Julia on ARM Radxa Rock Pro Quad Core

2014-11-29 Thread Jameson Nash
`killall -USR1 julia`

On Sun Nov 30 2014 at 2:36:37 AM Airhead Bit airhead...@gmail.com wrote:

 Finished compiling, Lots of warnings, %CPU at 299~310, Used your below
 test and mine is the same.
 How can we find what is spinning all the CPU cycles?


 https://lh4.googleusercontent.com/-ZtUw4ml2dXc/VHrI7joXJhI/AFs/VGb5yUeYq-8/s1600/htop.JPG


 On Saturday, November 29, 2014 9:17:33 PM UTC-7, Viral Shah wrote:

 However, upon building, it looks ok, and peakflops() which was crashing
 for me before works fine now.

 julia Base.LinAlg.BlasInt
 Int32

 julia Base.USE_BLAS64
 false


 -viral



  On 30-Nov-2014, at 9:31 am, Viral Shah vi...@mayin.org wrote:
 
  Interestingly, I get the same error now. I had cleaned out the whole
 openblas directory before starting the build.
 
  -viral
 
 
 

  On 30-Nov-2014, at 6:14 am, Isaiah Norton isaiah...@gmail.com wrote:
 
  You will probably need to do `make -C deps clean-openblas` first (or
 just remove the openblas-0.2.12 subdirectory).
 

  On Sat, Nov 29, 2014 at 7:01 PM, Airhead Bit airhe...@gmail.com
 wrote:
  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 airhe...@gmail.com 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?