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

GOG Installer stopped working #740

Closed
ksco opened this issue Apr 24, 2023 · 10 comments
Closed

GOG Installer stopped working #740

ksco opened this issue Apr 24, 2023 · 10 comments

Comments

@ksco
Copy link
Collaborator

ksco commented Apr 24, 2023

Collecting info for this system...
Operating system: linux
CPU Arch: x86_64
trying mojosetup in bin/linux/x86_64
USING en_US
Dynarec for RISC-V PageSize:4096 Running on unknown riscv64 cpu with 4 Cores
Params database has 25 entries
Box64 with Dynarec v0.2.3 922e5beb built on Apr 17 2023 15:40:30
BOX64_LD_LIBRARY_PATH: ./:lib/:lib64/
BOX64_PATH: ./:bin/
Counted 32 Env var
Looking for /tmp/selfgz395716368/bin/linux/x86_64/mojosetup
Rename process to "mojosetup"
Using native(wrapped) libpthread.so.0
Using native(wrapped) libdl.so.2
Using native(wrapped) libc.so.6
Using native(wrapped) ld-linux-x86-64.so.2
Using native(wrapped) libutil.so.1
Using native(wrapped) librt.so.1
Using native(wrapped) libm.so.6
NOTICE: scripts/mojosetup_init.lua:148: <eof> expected near 'end'
[hit enter]
@ptitSeb
Copy link
Owner

ptitSeb commented Apr 24, 2023

I reproduce that also on ARM64 machine. It seems to be an issue with load/unload of libs (I guess). I'll debug that tomorrow.

I mean, I have a crash on my side, because of missing libncursesw.so.5, no issue unpacking, which might be a different issue after all

@ksco
Copy link
Collaborator Author

ksco commented Apr 24, 2023

Last week I tried it was working well, so something recently introduced this issue.

@ksco
Copy link
Collaborator Author

ksco commented Apr 24, 2023

Interesting. If you run it from a different directory than where the GOG install script sits, it works fine.

@ksco
Copy link
Collaborator Author

ksco commented Apr 28, 2023

Is this fixed on ARM64? I haven't figured out what the cause is in RV64, but it seems not related to box64.

@ptitSeb
Copy link
Owner

ptitSeb commented Apr 28, 2023

I could run GOG installer on ARM64 after the fix yes. But I'm not sure we had the exact same issue.

@ksco
Copy link
Collaborator Author

ksco commented Apr 28, 2023

Can you run the installer from the current folder? e.g. cd Downloads && ./some_gog_installer.sh. I have to run it with Downloads/some_gog_installer.sh, the former way will cause an error.

@ptitSeb
Copy link
Owner

ptitSeb commented Apr 28, 2023

I run installer with BOX64_BASH=~/git/box64/tests/bash box64 ./some_installer.sh on my side, to use x86_64 bash and box64

@ksco
Copy link
Collaborator Author

ksco commented Apr 28, 2023

Yes, I'm assuming we are in a box64 x86_64 bash above. Anyway, if this works on ARM64, can you try it on VF2 then? Don't know if it's something wrong with my environment.

@ptitSeb
Copy link
Owner

ptitSeb commented Apr 28, 2023

I just tried on RV64 with ftl installer, from the download folder, and it works fine. I launched the gtk2 installer with no issue (still a bit slow tho).

@ksco
Copy link
Collaborator Author

ksco commented Apr 28, 2023

Ok, then it must be something off on my side. It's not a box64 issue, so I'll close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants