-
Notifications
You must be signed in to change notification settings - Fork 20
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Request] river-git #937
Comments
I'm interested in solving this as it may help others.
The biggest difference between chaotic's build and building it yourself is that we build in a clean chroot (a separated container with only
|
Sure, here's the working .pkg.tar.zst generated by paru. The file host automatically renames files, sorry 馃槄. River's pretty similar to spectrwm except written in Wayland. |
Considering that my files are bigger than yours, and the error " Which according to Wikipedia: ""Intel introduced BMI2 together with BMI1 in its line of Haswell processors. Only AMD has produced processors supporting BMI1 without BMI2; BMI2 is supported by AMDs Excavator architecture and newer."" Does zig add |
@Mrfiregem, please try this one: The only difference is that I built with |
This still results in a similar error message.
The xwayland errors are just because apparently the jobs were still running after exiting with error and were taking up the sockets. As for your earlier question, I'm unfamiliar with how zig compiles programs. |
Pff, another BMI2 instruction.
No problem, river's author answered me in IRC. I'm just studying which solution does not impact ArchLinux's makeflags. |
@dr460nf1r3 can you remove this package while I find a fix for this? |
Sure :) Didnt mean to close this though, lol |
馃悰 For reporting bugs
When loading from a display manager or greeter, you're immediately brought back. Running
river
in the terminal results in an error:River should launch on both instances. There's no problem when compiling myself or running
paru aur/river-git
. If this isn't fixable on your end, maybe remove this package from the repo since this happens every update and may mess people up when they wonder why their wm won't boot.The text was updated successfully, but these errors were encountered: