![]() I forgot I'd done this, but before the second attempt I downgraded rust to rust-1 1.71.0-1-x86_64. from the Artix archive, as this predates the problem versions and my first try failed during a rustc bit. I built on the HDD not in /tmp and RAM, after building I only have about 16GB free space on the partition, there was less than 64GB even adding free HDD space when I started, swap and RAM together. I was just building on my regular OpenRC install on my Dell E7470, not in a clean chroot, which has a 4th generation I7 CPU, a low power consumption type so only 4 threads available as this is a lightweight portable laptop. It built using clang, I think it is possible to build with gcc as an alternative but that is what it did by default. This was the PKGBUILD I used, and I updated just before building, because it needed to install clang and llvm. ![]() You could even be experiencing a bug from something else related to the build process, no 128GB was required here. ![]() If that doesn't work, if you post more details people might be able to help more, ie your PKGBUILD, system spec, build failure messages, how many threads you are using - this could be configured in various places, /etc/nf, the PKGBUILD, or a custom. If you look at the AUR page then on the right there is a link View Changes which will show you this - there has actually been another change now since I built it. It could be this as mentioned in the other thread: This changed in the librewolf PKGBUILD when 116 was introduced: -ac_add_options -enable-lto=cross +ac_add_options -enable-lto=cross,full That's the only significant change during that period, and lto = LINK time optimisation which is going to affect linking. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |