From: ludo@gnu.org (Ludovic Courtès)
To: Martin Castillo <castilma@uni-bremen.de>
Cc: 31023@debbugs.gnu.org
Subject: bug#31023: --verbosity=4 breaks build?
Date: Mon, 02 Apr 2018 23:48:03 +0200 [thread overview]
Message-ID: <87y3i5e0vg.fsf@gnu.org> (raw)
In-Reply-To: <03246993-5134-5605-08f7-5fcea91e5c64@uni-bremen.de> (Martin Castillo's message of "Mon, 2 Apr 2018 17:12:48 +0200")
Hello Martin,
As a foreword, note that ‘--verbosity’ is almost useless, even to Guix
developers. I think we should hide it under a weird name, maybe
‘--daemon-debug’?
Martin Castillo <castilma@uni-bremen.de> skribis:
> I found this while trying to test offloading.
> The both attached logs are the results of
>
> guix build grep --no-substitutes -M 1 --verbosity=3 2>buildsuc
> guix build grep --no-substitutes -M 1 --verbosity=4 2>builderr
> # I aborted the first after a few seconds
I don’t see anything fishy in ‘builderr’. What makes you think it
failed?
> The command was executed on guixsd with guix 0.14.0.3450-be5ed.
> Using -M 0 it tells me to increase -M or enabled distributed builds,
> even though guix offload test succeds. The offload machine is a
> raspberry pi. Is guix able to crosscompile when offloading on other
> architectures?
Your Raspberry will handle the build if and only if you’re requesting an
armhf-linux build. That is, if your machine is an x86_64 box, you’ll
want to type:
guix build grep -s armhf-linux
in which case the build will go to the Raspberry.
Note that this is *not* cross-compilation. It’s simply native
compilation offloaded to a separate machine.
For cross-compilation, see ‘--target’:
https://www.gnu.org/software/guix/manual/html_node/Additional-Build-Options.html
HTH,
Ludo’.
next prev parent reply other threads:[~2018-04-02 21:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 15:12 bug#31023: --verbosity=4 breaks build? Martin Castillo
2018-04-02 21:48 ` Ludovic Courtès [this message]
2018-04-06 15:32 ` Martin Castillo
2018-04-06 13:12 ` Ludovic Courtès
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=87y3i5e0vg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=31023@debbugs.gnu.org \
--cc=castilma@uni-bremen.de \
/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.