#asahi · 2023-11-22 16:30
zealouscupuacucould you maybe refer to the discussion in nixos about libunwind, that might be helpful to mention as well#asahi · 2023-11-22 16:30
zealouscupuacuI will link to relates issues in other repositories and maybe that's enough for moving this forward.#asahi · 2023-11-22 16:28
zealouscupuacuI understand their concerns but I am also unable to come up with firm proof it's fine to do the change.#asahi · 2023-11-22 16:18
zealouscupuacuthanks for all the pointers and also thanks for the great work on nixos with asahi, I am having a blast with it :)#asahi · 2023-11-22 16:14
zealouscupuacuI proposed a fix for babashka specifically but the maintainer has a really good point that it should be fixed for all GraalVM packages. But there are also concerns of the impact of such changes.#asahi · 2023-11-22 16:13
zealouscupuacuto be more specific, this might be an issue with all packages being built with GraalVM on NixOS. GraalVM by default uses the value of host for -H:PageSize and NixOS apparently runs on a 4K aarch64 kernel. Although they install fine, they fail to run altogether. Examples are babashka and clojure-lsp. By compiling those packages with -H:PageSize=64K they all work.#asahi · 2023-11-22 16:10
zealouscupuacuwould it cause the program to consume more memory or have any difference in performance?#asahi · 2023-11-22 16:07
zealouscupuacuI am trying to understand the impact of such change and arguments in favor of it. mainly to explain to package maintainers why such a change might be necessary and the pros and cons of it.#asahi · 2023-11-22 16:05
zealouscupuacuhey folks, is there a place where I can find information around compiling ARM programs using 64K page size vs other page sizes.