From: Michael Zucchi <notzed@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>, help-guix@gnu.org
Subject: Re: jfs, jfsutils?
Date: Tue, 31 Dec 2019 10:08:44 +1030 [thread overview]
Message-ID: <32c9e2f2-4028-9e22-f0d2-3a3813d17f64@gmail.com> (raw)
In-Reply-To: <87y2viifel.fsf@nckx>
On 12/12/19 10:27 am, Tobias Geerinckx-Rice wrote:
>
> If you're completely new to Guix that might sound daunting, but it's
> honestly not that hard and you should get plenty of help on the
> mailing list and/or on IRC.
>
Sorry Tobias, but I haven't been able to progress any further on this.
As far as I can tell the guix boostrap process doesn't support
amd64-only systems so although I can compile it, it doesn't pass 'make
check' and so I didn't try further. 32-bit executables are disabled in
my kernel and bootstrap.scm just assumes they work based on the
architecture.
I asked on IRC but I'm in the 'wrong' timezone to get any useful
responses and a query to the mailing list went unanswered.
Also, sort of related and I know it's not guix's fault but it's somewhat
difficult to find anything useful about guix using any search engine.
Regards,
Z
next prev parent reply other threads:[~2019-12-30 23:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 22:31 jfs, jfsutils? Michael Zucchi
2019-12-11 22:38 ` Josh
2019-12-11 23:49 ` Michael Zucchi
2019-12-11 23:57 ` Tobias Geerinckx-Rice
2019-12-12 1:41 ` Tobias Geerinckx-Rice
2019-12-12 3:18 ` Michael Zucchi
2019-12-13 14:31 ` Joshua Branson
2019-12-13 16:07 ` Tobias Geerinckx-Rice
2019-12-13 16:23 ` Tobias Geerinckx-Rice
2019-12-14 1:15 ` Michael Zucchi
2019-12-30 23:38 ` Michael Zucchi [this message]
2019-12-31 0:42 ` Josh Marshall
2019-12-31 6:26 ` Michael Zucchi
2020-01-05 19:04 ` Gábor Boskovits
2020-01-06 7:20 ` Michael Zucchi
2019-12-13 14:33 ` Packing bcachefs " Joshua Branson
2019-12-13 15:32 ` Packaging bcachefs Tobias Geerinckx-Rice
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=32c9e2f2-4028-9e22-f0d2-3a3813d17f64@gmail.com \
--to=notzed@gmail.com \
--cc=help-guix@gnu.org \
--cc=me@tobias.gr \
/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.