I did usr/bin/julia-debug-basic instead. It ran for a while and then closed
after giving a system error warning.
And the terminal screen rolls down with lots of data. Is it supposed to
create an image that I should post?
Not clear. I also see julia-debug-readline but no julia.
Thanks


On Sun, Jan 26, 2014 at 7:52 PM, Rajan Gurjar <[email protected]> wrote:

> rajan@rajan-Aspire-5742Z:~/julia/base$ strace /usr/bin/julia --build
> output sysimg.jl
> strace: Can't stat '/usr/bin/julia': No such file or directory
>
>
>
> On Sun, Jan 26, 2014 at 7:41 PM, Elliot Saba <[email protected]>wrote:
>
>> Nope, sometimes VMs can cause an illegal instruction error.
>>
>> What is the output of `strace ../usr/bin/julia --build output sysimg.jl`?
>>  Execute that inside of the `base` folder.
>> -E
>>
>>
>> On Sun, Jan 26, 2014 at 4:19 PM, Rajan Gurjar <[email protected]>wrote:
>>
>>> No, but I do have a VM installed. Not using it though for Julia.
>>> Do you think I should try it instead?
>>>
>>>
>>> On Sun, Jan 26, 2014 at 6:18 PM, Elliot Saba <[email protected]>wrote:
>>>
>>>> Rajan, are you running inside of a VM?
>>>>
>>>>
>>>> On Sun, Jan 26, 2014 at 1:46 PM, Rajan Gurjar <[email protected]>wrote:
>>>>
>>>>> Just tried "make debug" after "make clean"
>>>>> but exactly the same output as before
>>>>> LINK usr/bin/julia-debug-readline
>>>>>     CC ui/repl-basic.do
>>>>>     LINK usr/bin/julia-debug-basic
>>>>>
>>>>> osutils.jl
>>>>> Illegal instruction (core dumped)
>>>>> make[1]: *** [/home/rajan/julia/usr/lib/julia/sys0.bc] Error 132
>>>>> make: *** [debug] Error 2
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Jan 26, 2014 at 3:54 PM, Rajan Gurjar <[email protected]>wrote:
>>>>>
>>>>>> processor    : 0
>>>>>> vendor_id    : GenuineIntel
>>>>>> cpu family    : 6
>>>>>> model        : 37
>>>>>> model name    : Intel(R) Pentium(R) CPU        P6100  @ 2.00GHz
>>>>>> stepping    : 5
>>>>>> microcode    : 0x2
>>>>>> cpu MHz        : 933.000
>>>>>> cache size    : 3072 KB
>>>>>> physical id    : 0
>>>>>> siblings    : 2
>>>>>> core id        : 0
>>>>>> cpu cores    : 2
>>>>>> apicid        : 0
>>>>>> initial apicid    : 0
>>>>>> fpu        : yes
>>>>>> fpu_exception    : yes
>>>>>> cpuid level    : 11
>>>>>> wp        : yes
>>>>>> flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>>>>>> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe 
>>>>>> syscall
>>>>>> nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
>>>>>> nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr
>>>>>> pdcm pcid popcnt lahf_lm arat dtherm
>>>>>> bogomips    : 3990.03
>>>>>> clflush size    : 64
>>>>>> cache_alignment    : 64
>>>>>> address sizes    : 36 bits physical, 48 bits virtual
>>>>>> power management:
>>>>>>
>>>>>> processor    : 1
>>>>>> vendor_id    : GenuineIntel
>>>>>> cpu family    : 6
>>>>>> model        : 37
>>>>>> model name    : Intel(R) Pentium(R) CPU        P6100  @ 2.00GHz
>>>>>> stepping    : 5
>>>>>> microcode    : 0x2
>>>>>> cpu MHz        : 1999.000
>>>>>> cache size    : 3072 KB
>>>>>> physical id    : 0
>>>>>> siblings    : 2
>>>>>> core id        : 2
>>>>>> cpu cores    : 2
>>>>>> apicid        : 4
>>>>>> initial apicid    : 4
>>>>>> fpu        : yes
>>>>>> fpu_exception    : yes
>>>>>> cpuid level    : 11
>>>>>> wp        : yes
>>>>>> flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>>>>>> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe 
>>>>>> syscall
>>>>>> nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology
>>>>>> nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr
>>>>>> pdcm pcid popcnt lahf_lm arat dtherm
>>>>>> bogomips    : 3990.03
>>>>>> clflush size    : 64
>>>>>> cache_alignment    : 64
>>>>>> address sizes    : 36 bits physical, 48 bits virtual
>>>>>> power management:
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Jan 26, 2014 at 2:27 PM, Jameson Nash <[email protected]>wrote:
>>>>>>
>>>>>>> I think he mentioned this was a clean build, from scratch.
>>>>>>>
>>>>>>> Rajan, what's your processor? also try `make debug` and see if that
>>>>>>> prints anything more when in crashes
>>>>>>>
>>>>>>> On Sun, Jan 26, 2014 at 2:21 PM, Tim Holy <[email protected]>
>>>>>>> wrote:
>>>>>>> > On Sunday, January 26, 2014 11:16:24 AM Rajn wrote:
>>>>>>> >> Bump anyone? What does this mean? Next steps please?
>>>>>>> >
>>>>>>> > Have you tried "make clean; make"?
>>>>>>> > --Tim
>>>>>>> >
>>>>>>> >>
>>>>>>> >> osutils.jl
>>>>>>> >> Illegal instruction (core dumped)
>>>>>>> >> make[1]: *** [/home/rajan/julia/usr/lib/
>>>>>>> >> julia/sys0.bc] Error 132
>>>>>>> >> make: *** [release] Error 2
>>>>>>> >>
>>>>>>> >> On Friday, January 24, 2014 10:30:18 PM UTC-5, Rajn wrote:
>>>>>>> >> > After my several failed attempts to run PyPlot through Julia in
>>>>>>> Windows, I
>>>>>>> >> > decided to give up and try Linux.
>>>>>>> >> > Guess it was even worse.
>>>>>>> >> >
>>>>>>> >> > First I added to regular repository (not the nightlybuild)
>>>>>>> >> > then added the dep-repository
>>>>>>> >> > then updated and
>>>>>>> >> > then installed julia
>>>>>>> >> >
>>>>>>> >> > Here's the latest:
>>>>>>> >> > Unpacking librmath-dev (from
>>>>>>> >> > .../librmath-dev_2.15.2-juliadeps2~raring_amd64.deb) ...
>>>>>>> >> > dpkg: error processing
>>>>>>> >> >
>>>>>>> /var/cache/apt/archives/librmath-dev_2.15.2-juliadeps2~raring_amd64.deb
>>>>>>> >> >
>>>>>>> >> > (--unpack):
>>>>>>> >> >  trying to overwrite '/usr/include/Rmath.h', which is also in
>>>>>>> package
>>>>>>> >> >
>>>>>>> >> > r-mathlib 3.0.1-3ubuntu1
>>>>>>> >> > No apport report written because MaxReports is reached already
>>>>>>> >> >
>>>>>>> >> >
>>>>>>> Selecting
>>>>>>> >> >
>>>>>>> >> > previously unselected package julia.
>>>>>>> >> > Unpacking julia (from .../julia_0.2.0~saucyfinal1_amd64.deb) ...
>>>>>>> >> > Processing triggers for man-db ...
>>>>>>> >> >
>>>>>>> >> > Errors were encountered while processing:
>>>>>>> >> >
>>>>>>>  /var/cache/apt/archives/librmath-dev_2.15.2-juliadeps2~raring_amd64.deb
>>>>>>> >> >
>>>>>>> >> > E: Sub-process /usr/bin/dpkg returned an error code (1)
>>>>>>> >> >
>>>>>>> >> > Have no clue absolutely how to proceed. The same issue occurs
>>>>>>> when I try
>>>>>>> >> > nightly builds.
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>

Reply via email to