From: Svante Signell <svante.signell@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Status update+patches:Re: I managed to build guix natively on Debian GNU/Hurd , what's next?
Date: Tue, 03 Sep 2019 16:34:51 +0200 [thread overview]
Message-ID: <22f1e536522d303a01dbdaac3dcd54360f09730a.camel@gmail.com> (raw)
In-Reply-To: <62954aca574f56f1cb980b147fb4f3d8a492632c.camel@gmail.com>
On Tue, 2019-09-03 at 15:56 +0200, Svante Signell wrote:
> I did not look at the console, but found out similar crashes there. How did
> you get the output to the client terminal instead of the qemu console (not
> possible to cut and paste from that)? I have now tested both the statically
> built tar, the native tar downloaded by guix and the native tar: No errors
> now.
> How can I rebuild from scratch to watch the output on the console?
>
This time bash crashed... Took a screen shot of the qemu console. I have to
replace all four: bash mkdir tar xz and put them into the .xz file too.
next prev parent reply other threads:[~2019-09-03 14:34 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 19:25 I managed to build guix natively on Debian GNU/Hurd , what's next? Svante Signell
2019-08-29 22:51 ` Svante Signell
2019-08-29 23:36 ` Ricardo Wurmus
2019-08-30 12:00 ` Svante Signell
2019-08-30 17:14 ` Julien Lepiller
2019-08-30 18:25 ` Svante Signell
2019-08-30 21:07 ` Svante Signell
2019-08-30 21:30 ` Ricardo Wurmus
2019-08-30 21:52 ` Svante Signell
2019-08-30 22:17 ` Ricardo Wurmus
2019-08-31 8:06 ` Svante Signell
2019-08-31 8:13 ` Julien Lepiller
2019-08-31 9:24 ` Svante Signell
2019-08-31 9:41 ` Julien Lepiller
2019-08-31 12:12 ` Ricardo Wurmus
2019-08-31 17:27 ` Svante Signell
2019-09-01 9:11 ` Svante Signell
2019-09-01 9:32 ` Efraim Flashner
2019-09-01 13:28 ` Svante Signell
2019-09-01 18:01 ` Svante Signell
2019-09-03 12:07 ` Status update+patches:Re: " Svante Signell
2019-09-03 12:58 ` Ricardo Wurmus
2019-09-03 13:56 ` Svante Signell
2019-09-03 14:34 ` Svante Signell [this message]
2019-09-03 21:13 ` Svante Signell
2019-09-03 21:26 ` Ricardo Wurmus
2019-09-03 21:46 ` Svante Signell
2019-09-03 22:01 ` Ricardo Wurmus
2019-09-04 4:31 ` Svante Signell
2019-09-04 6:25 ` Svante Signell
2019-09-04 7:52 ` Ricardo Wurmus
2019-09-04 18:24 ` Svante Signell
2019-09-04 21:44 ` Ricardo Wurmus
2019-09-08 20:55 ` Ludovic Courtès
2019-09-10 8:10 ` Svante Signell
2019-09-20 15:59 ` Svante Signell
2019-09-20 17:03 ` Ricardo Wurmus
2019-09-20 17:49 ` Svante Signell
2019-09-20 18:48 ` Svante Signell
2019-09-20 19:12 ` Jonathan Brielmaier
2019-09-21 11:26 ` Svante Signell
2019-09-21 16:47 ` Svante Signell
2019-09-22 8:45 ` Need help: Re: Status update+patches:Re: I managed to ... GNU/Hurd Svante Signell
2019-09-24 13:06 ` Summary Re: Need help: " Svante Signell
2019-09-20 22:18 ` Status update+patches:Re: I managed to build guix natively on Debian GNU/Hurd , what's next? Ricardo Wurmus
2019-09-21 8:10 ` Svante Signell
2019-08-30 21:56 ` Julien Lepiller
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=22f1e536522d303a01dbdaac3dcd54360f09730a.camel@gmail.com \
--to=svante.signell@gmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).