-
-
Notifications
You must be signed in to change notification settings - Fork 312
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
More wrapped functions are required to run xterm #1990
Comments
Maybe it would be easier to just wrap libXaw.so.7 instead? |
I am interested in developing wrappers for Could you provide a detailed guide to approach this library wrapping challenge? |
Youc an start with https://box86.org/2024/02/how-to-create-a-wrapping/ There is also the new wrapperhelper that can help a lot. |
Out of curiosity, what's the use case to run xterm with box64 on an x86_64 machine? |
I came across this while trying to run xclock which also depends on libXaw.so.7 While I can't speak for @jserv my use case for running the x86_64 build of xclock was I thought it would be easier to run than steam and would help check my box64 is was able to run code ok. Turns out it wasn't easier! xclock has even more symbols missing than xterm! Not sure it'll help progress this issue any further but here is the output from xclock:
I seem to have ended up with a x86_64-linux-gnu and box64-x86_64-linux-gnu folders. Box64 seems to be looking at x86_64-linux-gnu and maybe that's breaking things? The output was the same on my Pi5 which has steam running OK, so I'm not sure what the issue is with my Rock5B, other than it not being a Debian based distro and I'm having to manually install a few things or create Gentoo ebuilds where I can. As aside, is there a simple X86_64 program I can copy from my laptop to test Box64 with? |
I wrapped libXaw instead. box64 (and box86) primary target is games. So games are the kind of software that are the most tested. And they tend to use a minimum set of X11 features. And manytime, no X11 feature at all while relying on SDL2 for example. Anything simple based on SDL1/SDL2 would be better. Now that libXaw is wrapped, I suppose XClock might work tho. |
Wow that was quick thank you. I should probably try and run the ctest program from box64? I didn't expect to wrap the library. I started reading the wrapper blog but still a bit over my understanding at the moment. I now just have two errors.
|
When attempting to run xterm on a Debian unstable system with x86-64 architecture using box64, the emulation encountered multiple symbol resolution issues in the Xaw library. Specifically, box64 failed to find and correctly map several global symbols required by
libXaw.so.7
, including:To successfully emulate the Xaw library, box64 requires additional function wrappers to be implemented, ensuring comprehensive symbol resolution and compatibility across different architectural environments.
The text was updated successfully, but these errors were encountered: