diff options
Diffstat (limited to '')
| -rw-r--r-- | results/scraper/box64/63 | 6 | ||||
| -rw-r--r-- | results/scraper/box64/634 | 2 | ||||
| -rw-r--r-- | results/scraper/box64/635 | 46 | ||||
| -rw-r--r-- | results/scraper/box64/639 | 10 |
4 files changed, 64 insertions, 0 deletions
diff --git a/results/scraper/box64/63 b/results/scraper/box64/63 new file mode 100644 index 000000000..d4141fbf7 --- /dev/null +++ b/results/scraper/box64/63 @@ -0,0 +1,6 @@ +Missing lib downloader support +I have written a small script that downloads and extracts the missing libs automatically on being provided the name logged by box64 as a missing lib. It is a hasel to keep downloading and running only to find another dependency missing. + +Is there a recommendation or any roadmap about incorporating something similar into box64/86 ? + +I can share the bash script if not so. \ No newline at end of file diff --git a/results/scraper/box64/634 b/results/scraper/box64/634 new file mode 100644 index 000000000..5d6c9ddae --- /dev/null +++ b/results/scraper/box64/634 @@ -0,0 +1,2 @@ +[DYNAREC] Introducing differential testing to box64 JIT +When porting dynarec to RISC-V, @ksco and I found that many long and less frequent x86_64 opcodes are not well tested, so we are unaware of hidden bugs inside. By introducing fuzzing tests like csmith, we have more chance to detect such bugs. But the problem with csmith is that it generates very few 8-bit and 16-bit math operations, so related opcodes are rarely tested. I suggested to use sed to replace `int32_t` with `int8_t`, making gcc produce a bunch of unimplemented opcodes, but this breaks the checksum mechanism of csmith. In order to verify the correctness of JIT implementation, we probably need to compare x86_64 registers between dynarec and the interpreter, side by side, for each translated instruction. With differential testing infrastructure, we can better debug dynarec and find bugs easily and precisely. \ No newline at end of file diff --git a/results/scraper/box64/635 b/results/scraper/box64/635 new file mode 100644 index 000000000..610c15a35 --- /dev/null +++ b/results/scraper/box64/635 @@ -0,0 +1,46 @@ +Running Stardew Valley on VisionFive 2 +I'm trying to run Stardew Valley on the VisionFive 2 SBC, and encountered the following errors, what should I do to fix this? + +``` +Dynarec for RISC-V PageSize:4096 Running on unknown riscv64 cpu with 4 Cores +Params database has 22 entries +Box64 with Dynarec v0.2.3 5e680e0f built on Mar 25 2023 03:53:49 +Using default BOX64_LD_LIBRARY_PATH: ./:lib/:lib64/:x86_64/:bin64/:libs64/ +BOX64 will force the used of emulated libs for libSDL2-2.0.so.0 +Using default BOX64_PATH: ./:bin/ +Counted 27 Env var +Looking for Stardew Valley +Rename process to "Stardew Valley" +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 emulated /usr/lib/x86_64-linux-gnu/libstdc++.so.6 +Using native(wrapped) libm.so.6 +Using emulated /usr/lib/x86_64-linux-gnu/libgcc_s.so.1 +Using emulated /root/Downloads/squashfs-root/usr/lib/StardewValley/libhostfxr.so +Using emulated /root/Downloads/squashfs-root/usr/lib/StardewValley/libhostpolicy.so +Using emulated /root/Downloads/squashfs-root/usr/lib/StardewValley/libcoreclr.so +Warning: Global Symbol _ZTH12t_ThreadType not found, cannot apply R_X86_64_GLOB_DAT @0x3f9c1b1110 ((nil)) in /root/Downloads/squashfs-root/usr/lib/StardewValley/libcoreclr.so +Warning: Global Symbol _ZTH27t_pStackWalkerWalkingThread not found, cannot apply R_X86_64_GLOB_DAT @0x3f9c1b1128 ((nil)) in /root/Downloads/squashfs-root/usr/lib/StardewValley/libcoreclr.so +Warning: Global Symbol _ZTHN9StressLog19t_pCurrentThreadLogE not found, cannot apply R_X86_64_GLOB_DAT @0x3f9c1b1148 ((nil)) in /root/Downloads/squashfs-root/usr/lib/StardewValley/libcoreclr.so +Warning: Global Symbol _ZTH15t_CantStopCount not found, cannot apply R_X86_64_GLOB_DAT @0x3f9c1b1160 ((nil)) in /root/Downloads/squashfs-root/usr/lib/StardewValley/libcoreclr.so +Warning: Global Symbol _ZTH16t_CantAllocCount not found, cannot apply R_X86_64_GLOB_DAT @0x3f9c1b1250 ((nil)) in /root/Downloads/squashfs-root/usr/lib/StardewValley/libcoreclr.so +Warning: Weak Symbol __gmon_start__ not found, cannot apply R_X86_64_JUMP_SLOT @0x3f9c1b1650 (0x71e86) +Warning: Weak Symbol _ZTH12t_ThreadType not found, cannot apply R_X86_64_JUMP_SLOT @0x3f9c1b16e8 (0x71fb6) +Warning: Weak Symbol _ZTH27t_pStackWalkerWalkingThread not found, cannot apply R_X86_64_JUMP_SLOT @0x3f9c1b16f0 (0x71fc6) +Warning: Weak Symbol _ZTHN9StressLog19t_pCurrentThreadLogE not found, cannot apply R_X86_64_JUMP_SLOT @0x3f9c1b1708 (0x71ff6) +Warning: Weak Symbol _ZTH15t_CantStopCount not found, cannot apply R_X86_64_JUMP_SLOT @0x3f9c1b1710 (0x72006) +Warning: Weak Symbol _ZTH16t_CantAllocCount not found, cannot apply R_X86_64_JUMP_SLOT @0x3f9c1b1778 (0x720d6) +Error: Symbol pthread_mutexattr_setrobust not found, cannot apply R_X86_64_JUMP_SLOT @0x3f9c1b1e40 (0x72e66) in /root/Downloads/squashfs-root/usr/lib/StardewValley/libcoreclr.so +Error: Symbol pthread_mutex_consistent not found, cannot apply R_X86_64_JUMP_SLOT @0x3f9c1b1e58 (0x72e96) in /root/Downloads/squashfs-root/usr/lib/StardewValley/libcoreclr.so +Error: relocating Plt symbols in elf libcoreclr.so +Error initializing needed lib /root/Downloads/squashfs-root/usr/lib/StardewValley/libcoreclr.so +Failed to load /root/Downloads/squashfs-root/usr/lib/StardewValley/libcoreclr.so, error: Cannot dlopen("/root/Downloads/squashfs-root/usr/lib/StardewValley/libcoreclr.so"/0x369a3918, 1) + +FillBlock at (nil) triggered a segfault, cancelling +FillBlock at (nil) triggered a segfault, cancelling +1983|Ask to run at NULL, quit silently +``` \ No newline at end of file diff --git a/results/scraper/box64/639 b/results/scraper/box64/639 new file mode 100644 index 000000000..783bed932 --- /dev/null +++ b/results/scraper/box64/639 @@ -0,0 +1,10 @@ +packaging for Debian +Hi, + +I packaged box64 for Debian here: https://salsa.debian.org/debian/box64/ + +One of the problems I encountered was, that box64 tries to install files that are owned by the `libgcc-s1:amd64` and `libstdc++6:amd64` packages, namely `/lib/x86_64-linux-gnu/libgcc_s.so.1` and `/usr/lib/x86_64-linux-gnu/libstdc++.so.6`, respectively. This is a bit of a bummer because this means that the arm64 box64 package will have to conflict with both amd64 libraries. This in turn will make it impossible for a user who wants to install box64 to install any amd64 packages making use of the amd64 gcc and C++ libraries. + +Why is this important? Proprietary amd64 Debian packages that I'd like to try running with box64 will also depend on the gcc and C++ library packages. If the arm64 box64 package conflicts with the amd64 libraries, then I will be unable to install proprietary amd64 packages that I want to use with box64 to avoid having to use super slow QEMU user emulation. + +I wonder: do you think there is a way for the arm64 box64 package to co-exist with the amd64 gcc and C++ libraries? \ No newline at end of file |