-
Notifications
You must be signed in to change notification settings - Fork 122
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
Failure under wine #560
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
How to reproduce the issue
wine ros.exe
Expected behavior
Roswell does not segfault.
Investigating the problem
Running ros.exe with
-v
shows that it downloads latest sbcl (for its internal purposes I guess), tries to install it with msiexec and fails to do so, here's the excerpt from log:Segfault happens here because of
C:\users\root\.roswell\src\sbcl-2.3.4-x86-64-windows
directory being empty.I've experimented with the msiexec launch command (
C:\windows\system32\msiexec.exe /a "C:\users\root\.roswell\archives\sbcl-bin-2.3.4-x86-64-windows.msi" targetdir="C:\users\root\.roswell\src\sbcl-2.3.4-x86-64-windows" /qn /lv "C:\users\root\.roswell\impls\log\sbcl-bin-2.3.4-x86-64-windows\install.log"
) and found that running it with/i
switch ("install") instead of/a
("administrative install") seemingly makes it work. Is there any reason not to use the regular install in Roswell under Windows?The text was updated successfully, but these errors were encountered: