apteryks
apteryks
@thepowersgang OK, x86_64 can now build cargo again, but on i686-linux it fails early still with: ``` (15/112) BUILDING annotate_snippets from annotate-snippets v0.6.1 > /tmp/guix-build-rust-1.39.0.drv-0/mrustc/bin/mrustc rustc-1.39.0-src/vendor/annotate-snippets/src/lib.rs -o output/rustc-build/libannotate_snippets-0_6_1.rlib --crate-name annotate_snippets...
Nice! How did you find out about it?
Eh, it got really far this time, before failing on this: ``` (93/112) BUILDING rustc v0.0.0 > /tmp/guix-build-rust-1.39.0.drv-0/mrustc/bin/mrustc rustc-1.39.0-src/src/librustc/lib.rs -o output/rustc-build/librustc.rlib --crate-name rustc --crate-type rlib -C emit-depfile=output/rustc-build/librustc.rlib.d --crate-tag 0_0_0 -g...
I'd rather think we're hitting a 32-bit limit because building fails on a machine with 32 GiB of RAM and 16 GiB of swap: ``` $ free -h total used...
Sharing the experiment of another fellow Guix user: > With ./build-1.39.0.sh in mrustc, some help from #mrustc, and some local > patches, I was able to get it build under...
I'd suggest moving all the tests requiring proprietary software to their own repository and making it disabled by default. Until then, I've came up with the solution seen in the...
Hello! Could it be possible to fallback to using the package name when no cpe-name property is found in the package definition? We use this in GNU Guix, it seems...
civodul from #guix just mentioned that repology parses the data at 'guix.gnu.org/packages.json', which means a simple solution that doesn't require any change on your side would be to add the...
> I've asked about this on #guix a month ago. [...] If we fallback to package name as `cpe_product`, `CPE information is missing` problems will turn into `CPE unreferenced` problems...
@AMDmi3 hello, and thank you for this interesting query! I'll look at how the CPE name databases available are organized and see if we can improve our linter to do...