zv-io

Results 20 comments of zv-io

Hi, those are mine. I'll try to explain the reasons why I'm not attempting to upstream changes. First, let's consider Rich's repository to be a reference implementation. I make my...

> I am very interested in upstreaming any patches needed for Fortran to work, altho not building it by default. Ada too. Ada is a work in progress. My rule...

> @zv-io Hey, do you know what could be causing this? There is no errors during compile so not much to go on. But I think I remember you mentioning...

> Unfortunately, the build you linked has expired since artifacts are only retained for 90 days. However, I was able to run [v1.0.21](https://github.com/aristocratos/btop/releases/tag/v1.0.21) without issue. This was the first released...

> Any help in figuring out what's going on would be greatly appreciated. I will try to reproduce it on my own hardware and write back.

This is interesting. You can ignore this but I figured I'd share. ``` ubuntu@ubuntu:/dev/shm/btop$ make STATIC=true STRIP=false ADDFLAGS="-g -v" OPTFLAGS="-O0" -j4 CXX=/dev/shm/riscv64-linux-musl-native/bin/g++ ██████╗ ████████╗ ██████╗ ██████╗ ██╔══██╗╚══██╔══╝██╔═══██╗██╔══██╗ ██╗ ██╗ ██████╔╝...

It may not be musl per se, perhaps libstdc++ or something in that realm, or a miscompilation.

The segfault/crash is triggered when [0004-static-pie.patch](https://github.com/aristocratos/btop/files/8051966/0004-static-pie.txt) is applied to GCC and is unrelated to musl version, GCC version, or otherwise. I will investigate. The toolchains will need to be rebuilt...

Root cause appears to be https://sourceware.org/bugzilla/show_bug.cgi?id=22263.