all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Howard <christopher@librehacker.com>
To: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
Cc: 53857@debbugs.gnu.org
Subject: bug#53857: telegram-desktop: fails to build
Date: Wed, 9 Feb 2022 11:18:23 -0900	[thread overview]
Message-ID: <YgQhjyeyfGWoHUWy@theoden> (raw)
In-Reply-To: <713a002ee4b33eb9b3ebb07edf0034a4d1cdd053.camel@ist.tugraz.at>

Hi, when I try to build with `guix build -M 1 -c 1 telegram-desktop` I seem to be getting the same error. I can believe what you say about the ram, as I've run into that problem before with other packages, though it seems frustrating I can't use some kind of command line option or something to tell the linker/compiler/assembler to use less ram. Seems strange that any package should need more than a GB or two of ram to build (*end rant*).

One thing though: using the above command-line options, I see that the last message in the build log is:

```
error: in phase 'build': uncaught exception:
%exception #<&invoke-error program: "make" arguments: ("-j" "4") exit-status: 2 term-signal: #f stop-signal: #f> 
phase `build' failed after 254.0 seconds
command "make" "-j" "4" failed with status 2
```

Isn't using -M 1 in the guix build options supposed to translate to "make -j 1", or do I misunderstand?

Christopher Howard




  reply	other threads:[~2022-02-09 20:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07 18:32 bug#53857: telegram-desktop: fails to build Christopher Howard
2022-02-08  7:15 ` Liliana Marie Prikler
2022-02-09 20:18   ` Christopher Howard [this message]
2022-02-10  7:02     ` Liliana Marie Prikler
2022-02-10  7:06       ` Christopher Howard
2022-07-06  7:23 ` Neo Lynn via web
2022-07-06  7:54 ` Neo Lynn via web
2022-10-23 11:41 ` Liliana Marie Prikler
     [not found]   ` <Y1bHt5QxQPMrNain@theoden>
2022-10-24 18:30     ` Liliana Marie Prikler

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

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

  git send-email \
    --in-reply-to=YgQhjyeyfGWoHUWy@theoden \
    --to=christopher@librehacker.com \
    --cc=53857@debbugs.gnu.org \
    --cc=liliana.prikler@ist.tugraz.at \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.