-
-
Notifications
You must be signed in to change notification settings - Fork 232
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
wine is broken #983
Comments
This might be an esync of fsync issue? Did you tried with |
still nothing
|
Well, I don't know then. Can you do a bisect to find the exact commit that broke it? (I was thinking of the futexv syscall, that is needed for ESYNC iirc, that got enable lately, but it should still be disable for BAD_SIGNAL build, that should be used on RK3588 unless something change kernel side, so it must be something else) |
i have found commit d3d971d to break wine, the commit before: 2e589f4 still works |
Oh?! That one. Ummm, interesting. I have to think of a solution then. can you check if your armhf libc expose any of those symbols:
(you can use |
i hope i took the right lib, i found it in /usr/lib/arm-linux-gnueabihf
i see : |
Do you build the tip of master branch with "-D_TIME_BITS=32" or without it (the default _TIME_BITS is 64, and it's broken)? Can you compare the required symbols of both binaries, the faulty master and the working, earlier commit? The command if I'm not mistaken is |
i only used -D_TIME_BITS=32 for older working 2e589f4 since i had to (or else it errored), i didn't add it for d3d971d because i thought it would cause more issues and it wasn't mentioned in COMPILE.md anyway but i recompiled the d3d971d and master (c5bccdf) with -D CMAKE_C_FLAGS="-D_TIME_BITS=32" and winecfg is working now!
build-master-broken.txt = faulty master (no -D_TIME_BITS=32) build-master-time.txt = working master (yes -D_TIME_BITS=32) build-test.txt = faulty d3d971d (no -D_TIME_BITS=32) build-time32.txt = working d3d971d (yes -D_TIME_BITS=32) build-working.txt = working earlier commit 2e589f4 (yes -D_TIME_BITS=32) (cant build 2e589f4 without -D_TIME_BITS=32 or it errors) diff between working earlier commit 2e589f4 and master compiled with -D_TIME_BITS=32 is that master has those extra lines:
the difference between master compiled without -D_TIME_BITS=32 and working earlier commit 2e589f4 is: master without -D_TIME_BITS=32 has this:
while working earlier commit 2e589f4 with -D_TIME_BITS=32 has:
|
For now I'd suggest either:
|
Can you update box86 and try again, see if it's fixed now? |
sorry for answering late, i have a build error (building 66a91b8, cmake .. -D RK3588=1 -D CMAKE_BUILD_TYPE=RelWithDebInfo)
|
I found this post last month when I came across the exact same issue, also on an orange pi 5 rk3588s running joshua-riek/ubuntu-rockchip OS 24.04. Nothing seems to happening- should I give up waiting and try v0.3.6? |
I pushed something that might help with the build issue. |
Wow, thanks for the quick response. Unfortunately it doesn't seem to make any difference
|
Ok, I pushed a new attempt. Hopefully it will work this time. |
It works! You, sir, are a legend. |
I have this same issue when installing the box86-rpi4arm64 as of today, as I don't have a toolchain to compile 32 bits. Is this version missing the fix? |
This ticket is a bit messy now, there is multiple issue in there, and some are fixed. I would suggest we close this ticket and you open a new clean one @lilezek |
I'm happy to, but I think I have exactly the same issue. The OP is using an orange pi 5 and I'm using rpi5 with the prebundled box86/box64 for raspberry pi 4 on a 64-bit OS. |
The exact same... as in the 1st post? |
if that's the case, try with |
wine no longer works on my orange pi 5 since d3d971d (rk3588s, joshua-riek/ubuntu-rockchip OS 24.04), box86 v0.3.7 d3d971d and fcbebfa and c5bccdf, Kron4ek/Wine-Builds, tested 9.13 and many older wine
it works again when i revert to stable release v0.3.6 and 2e589f4 (and build it with -D CMAKE_C_FLAGS="-D_TIME_BITS=32")
trying to run winecfg
trying to run winecfg with BOX86_LOG=1
The text was updated successfully, but these errors were encountered: