Kirin Etheridge
Kirin Etheridge
> Yeah, I got my system broken today after a regular upgrade. Portage was upgraded to 3.0.54 and doesn't work anymore! I had to `emerge -c` this package, [modify](https://github.com/kir68k/xira/blob/3d486520a9f5516b5d8aff605587495e1e91222d/sys-config/stylize/stylize-0.1.1.ebuild#L58) the...
> You can also replace the offending line with this: > > `local lto_overlay_dir="$("$(command -pv portageq)" get_repo_path ${PORTAGE_CONFIGROOT} lto-overlay)"` This seems like a temporary workaround, still hacking on with portageq.
The issue still persists, I'm using the clang profile with version 16.0.6 and get this bug. Seems to be caused by `gcc-fullversion` inside of `pkg_setup()`, at least I presume. Looking...
> @emrakyz Do you know any alternative until this point? I have a plan to incorporate some ideas (like ltoize's make.conf.lto) and maybe packages from this overlay into mine, with...
> I think for now you could try to have ltoize in your overlay, and update the ebuild to have an `if then else` part for both gcc and clang/llvm....
Running `cargo update` and generating a Cargo.lock [patch](https://github.com/kir68k/KRXT_portlay/blob/stream/app-misc/colorgen-nvim/files/rustc-1.71-deps.patch)*, which is passed to the package manager, fixes the issue and the program works as expected with the provided test toml file....
Oh, I thought 1.71 would be stable, with the main website stating 1.71.1 to be the latest stable? Sorry, I'm not too familiar with Rust *yet*. To clarify a bit,...
~~I think that's it actually. Using `cargo-bin-1.71.0 check -vv` gives something odd:~~ ```bash LD_LIBRARY_PATH='/home/kir68k/Documents/Git/Dissociated/colorgen-nvim/target/debug/deps:/usr/lib/rust/9999/lib' rustc ``` ~~So it uses the 9999 (live/git version) lib directory for Rust, and doesn't call...
Didn't know of that, I retract my statement about future versions then. The crater project you've mentioned reminds me of Stackage for Haskell, which I'm more familiar with. Anyhow, have...
I don't use this program, but found this issue at the top of Google when searching the same error. I think it's more so a steam/bwrap issue, as I get...