my "clients" want to validate the "build & custom" automation before thinking about upgrading. i have no choice :)
Le lundi 25 avril 2016 14:51:38 UTC+2, Michele Zaffalon a écrit : > > Would it not be better to update to 0.4.5 first? > > On Mon, Apr 25, 2016 at 1:57 PM, <ming...@irt-systemx.fr <javascript:>> > wrote: > >> it seems that >> >> /home/vagrant/julia-0.4.2/base/precompile.jl >> >> crashed because of memory overflow (i watched htop). >> >> i'll try the build with more memory on my test virtual machine (500Mb -> >> 1 Gb). >> >> >> >> Le lundi 25 avril 2016 13:50:21 UTC+2, ming...@irt-systemx.fr a écrit : >>> >>> hello, >>> >>> there a build issue on a Vagrant virtual machine (i am actually >>> debugging my Ansible automation) : >>> >>> require.jl >>> docs/helpdb.jl >>> docs/basedocs.jl >>> /home/vagrant/julia-0.4.2/base/precompile.jl >>> Killed >>> *** This error is usually fixed by running `make clean`. If the error >>> persists, try `make cleanall`. *** >>> make[1]: *** [/home/vagrant/julia-0.4.2/usr/lib/julia/sys.o] Error 1 >>> make: *** [julia-sysimg-release] Error 2 >>> vagrant@vagrant-ubuntu-trusty-64:~/julia-0.4.2$ make >>> LINK usr/lib/julia/sys.so >>> /home/vagrant/julia-0.4.2/usr/lib/julia/sys.o: file not recognized: File >>> truncated >>> collect2: error: ld returned 1 exit status >>> make[1]: *** [/home/vagrant/julia-0.4.2/usr/lib/julia/sys.so] Error 1 >>> >>> >>> and here is the sys.o file : >>> >>> vagrant@vagrant-ubuntu-trusty-64:~/julia-0.4.2/usr/lib/julia$ ll >>> total 3788 >>> drwxrwxr-x 2 vagrant vagrant 4096 Apr 25 13:27 ./ >>> drwxrwxr-x 4 vagrant vagrant 4096 Apr 25 13:23 ../ >>> -rw-r--r-- 1 vagrant vagrant 1966777 Apr 25 13:23 inference0.ji >>> -rw-r--r-- 1 vagrant vagrant 1898851 Apr 25 13:24 inference.ji >>> -rw-rw-r-- 1 vagrant vagrant 0 Apr 25 13:25 sys.o >>> >>> >>> i did : >>> make -j 1 >>> in order to be sure that it is not a parallel make issue. >>> >>> >>> bests, >>> >> >
