Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot run Julia.bat - Windows XP sp3 #3634

Closed
desjact opened this issue Jul 5, 2013 · 13 comments
Closed

Cannot run Julia.bat - Windows XP sp3 #3634

desjact opened this issue Jul 5, 2013 · 13 comments
Labels
bug Indicates an unexpected problem or unintended behavior system:windows Affects only Windows upstream The issue is with an upstream dependency, e.g. LLVM
Milestone

Comments

@desjact
Copy link

desjact commented Jul 5, 2013

julia.bat crashes and test-julia.bat give the message :
Your OS does not support AVX instructions. OpenBLAS is using Nehalem
kernels as a fallback, which may give you poorer performance.
Please submit a bug report with steps to reproduce this fault, and any error mes
sages that follow . Thanks.

When I hit enter it just closes.

Windows XP Pro SP3 machine with Intel i5-2500 @ 3.30Ghz
C:\julia-2b22323495\julia.bat

Is there anything else that I can supply you with to help debug this problem?
I have also tried to install Juliastudio. It opens the interface, but doesn't fully load Julia.
Sorry, I am new to this. But I would love to be able to use it.

Thanks

@Keno
Copy link
Member

Keno commented Jul 8, 2013

Can you try running julia.bat from a cmd prompt, so we can see if there are any error messages being printed. I will also take this opportunity to point out that Windows XP is beyond end-of-life and while I'll support it on a best-effort basis, it may very well not work with a future version of Julia.

@desjact
Copy link
Author

desjact commented Jul 8, 2013

I have attached a screenshot of the cmd promt.
Thank you for your help.

@Keno
Copy link
Member

Keno commented Jul 8, 2013

Screenshot didn't go through (I assume you attached it via email rather than on GitHub directly - GitHub truncates attachments).

@desjact
Copy link
Author

desjact commented Jul 8, 2013

error
Sorry, I hope this worked.
If not, it is really the same error as stated above. (In the first post)

@Keno
Copy link
Member

Keno commented Jul 8, 2013

Hmm, I don't think that OpenBlas warning should be a problem. @ViralBShah? @vtjnash Did you have an XP test machine?

@vtjnash
Copy link
Member

vtjnash commented Jul 8, 2013

It seems strange that OpenBLAS is not correctly detecting the Intel I5, although it shouldn't cause a crash. It would probably also be helpful if I were to print the actual error code instead of the generic error message (I had hoped windows would do it for me, like wine). I have successfully run julia on a Windows XP SP3 32-bit VirtualBox VM on julia.mit.edu.

@desjact
Copy link
Author

desjact commented Jul 8, 2013

Is there anything else I can do to help debug this?

@vtjnash
Copy link
Member

vtjnash commented Jul 10, 2013

I have a new binary up at http://s3.amazonaws.com/julialang/bin/winnt/x86/0.2/julia-0.2pre-964f411168-win32.exe, which may provide more information before quitting and may help me to better understand the problem.

@desjact
Copy link
Author

desjact commented Jul 16, 2013

error2
Thanks for the new binary and the quick response @vtjnash. I have uploaded the error.

@vtjnash
Copy link
Member

vtjnash commented Jul 18, 2013

Alright, I think this means that we are starting to run julia, but failing in the LLVM JIT almost immediately. The OpenBLAS warning also seems very suspicious. Is your platform 32 or 64 bit? There is a slim chance that the debugging info will be better if you edit the julia.bat file to run julia-debug-readline.exe, which may be helpful to me.

@desjact
Copy link
Author

desjact commented Jul 18, 2013

*update forgot to say that it's 32 bit
After modifying test-Julia.bat, this is the error

error3

@vtjnash
Copy link
Member

vtjnash commented Jul 23, 2013

This was a bug in LLVM with AVX detection. It appears to have been fixed in LLVM 3.3.

@vtjnash vtjnash closed this as completed Jul 23, 2013
@ViralBShah
Copy link
Member

Should we leave this open until we start producing binaries with LLVM 3.3?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Indicates an unexpected problem or unintended behavior system:windows Affects only Windows upstream The issue is with an upstream dependency, e.g. LLVM
Projects
None yet
Development

No branches or pull requests

4 participants