Hi Max, On Wed, Oct 12, 2022 at 4:24 AM Max Brieiev <max.brie...@gmail.com> wrote: > > Hi, > > Recently, Guix started building Emacs with native compilation. > > I did 'guix pull' few days ago (I hadn't done it for a few months), and > it broke my Emacs. > > The 'guix package -u emacs-next' finished building Emacs successfully. > > However, when I start Emacs, the native compiler starts doing it's job > and I see tons of compilation errors like this: > > Deleting /tmp/comp-lambda-RCGJQI.eln > comp--native-compile: Native compiler error: (lambda (&rest arg1) (let > ((f #'make-process)) (apply f arg1))), "Compiling > /tmp/comp-lambda-RCGJQI.eln... > x86_64-unknown-linux-gnu-gcc-10.3.0: fatal error: cannot execute ‘as’: > execvp: No such file or directory > compilation terminated. > > This seems to be something wrong with libgccjit dependency. > > If I understand correctly, it did its job successfully during build time > (since Emacs compiled successfully), but it fails now to compile > packages during runtime. Is it correct? > > How do I fix this?
I don't know of a fix, but Guix is tracking this issue here: https://issues.guix.gnu.org/issue/57878 I have been unable to upgrade Guix due to this issue. In my case it locks down my whole system with endless compilation processes. I wouldn't mind seeing native compilation disabled until upstream improves the experience, but it's been decided that native compilation is staying on. So, we're stuck on an old Guix until there's a solution. - Dave
