unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: eisbaer@tilde.team
Cc: help-guix@gnu.org
Subject: Re: Custom kernel config is not taken by guix
Date: Wed, 05 Apr 2023 12:14:01 +0000	[thread overview]
Message-ID: <87mt3mttau.fsf@kitej> (raw)
In-Reply-To: <a3d206aab99bc07a57f4e141681c90723dc050a1@tilde.team>

[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]

eisbaer@tilde.team skribis:

> Ok. Thank you! That worked. At least it compiles now... However I happen to get the following error during the compilation process:
>
> ====================
> zcat /var/log/guix/drvs/1l/3q5c3d89fv3dibynv55v3jqa4cdmxl-linux-libre-6.2.9.drv.gz
> ====================
>   AR      arch/x86/pci/built-in.a
>   CC      arch/x86/power/cpu.o
>   CC      arch/x86/power/hibernate_64.o
>   AS      arch/x86/power/hibernate_asm_64.o
>   CC      arch/x86/power/hibernate.o
>   AR      arch/x86/power/built-in.a
>   AR      built-in.a
>   AR      vmlinux.a
>   LD      vmlinux.o
> make[1]: *** [scripts/Makefile.vmlinux_o:61: vmlinux.o] Error 137
> make[1]: *** Deleting file 'vmlinux.o'
> make: *** [Makefile:1245: vmlinux_o] Error 2
> error: in phase 'build': uncaught exception:
> %exception #<&invoke-error program: "make" arguments: ("-j" "1") exit-status: 2 term-signal: #f stop-signal: #f> 
> phase `build' failed after 1951.1 seconds
> command "make" "-j" "1" failed with status 2

I think "Error 137" is the "out of memory" error for gcc and ld.
How much RAM do you have on this machine? Maybe it's not enough to
compile the Linux kernel...

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

      reply	other threads:[~2023-04-05 12:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22 16:07 Custom kernel config is not taken by guix eisbaer
2023-04-01 11:35 ` Guillaume Le Vaillant
     [not found] ` <5d0a15e9ab3f8ce31577650959327c950d215fec@tilde.team>
2023-04-04 13:54   ` Guillaume Le Vaillant
2023-04-04 18:34   ` eisbaer
2023-04-05 12:14     ` Guillaume Le Vaillant [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mt3mttau.fsf@kitej \
    --to=glv@posteo.net \
    --cc=eisbaer@tilde.team \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).