unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "christoph vogelsberg" <chrissvberg@gmx.de>
To: help-guix@gnu.org
Subject: General Question: What if Binary Building breaks?
Date: Fri, 24 Jun 2016 20:19:34 +0200	[thread overview]
Message-ID: <trinity-61fe21ed-9823-41fb-b0b8-8c8c901cdcf8-1466792374124@3capp-gmx-bs71> (raw)
In-Reply-To: <CAJ=RwfY7ib3qskG-tZpqOGqM4zfE+Ao0XWc2P-WY3ndWs6yWNg@mail.gmail.com>

Hello again GuixSD-ers

thanks for the last fast response! Now I face another question due to:

> > My question: is there an already elabored way, documentation and so
> > on, for this specific problem?
> 
> The solution is to build the software from source to produce a binary
> that is compatible with GuixSD.  Guix has a GNU Icecat package that
> may provide a good base for this.

I actually tried installing the IceCat package but my laptop got hang. It
was heavily virtualizing so I looked up hardware requirements for
building Firefox. I learned that 8GiB RAM (and therefor 64bit system) are
required. So this makes this package unbuildable for me.

Is there any solution for that case in general? I fear persons like me who
can't efford hardware like that need to wait until a prebuild is available.

Thanks in advance and thumbs up for your project!

cvog

  reply	other threads:[~2016-06-24 18:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21 23:21 General Question: Execution of binaries not built for GuixSD christoph vogelsberg
2016-06-22 10:50 ` Florian Paul Schmidt
2016-06-22 13:27   ` Florian Paul Schmidt
2016-06-22 13:53     ` Thompson, David
2016-06-22 14:06       ` ng0
2016-06-22 14:12       ` Florian Paul Schmidt
2016-06-22 12:44 ` Thompson, David
2016-06-24 18:19   ` christoph vogelsberg [this message]
2016-06-24 18:55     ` General Question: What if Binary Building breaks? ng0
2016-06-25 17:36     ` Leo Famulari

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=trinity-61fe21ed-9823-41fb-b0b8-8c8c901cdcf8-1466792374124@3capp-gmx-bs71 \
    --to=chrissvberg@gmx.de \
    --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).