From: Antero Mejr via Guix-patches via <guix-patches@gnu.org>
To: "(" <paren@disroot.org>
Cc: "55606@debbugs.gnu.org" <55606@debbugs.gnu.org>,
Tobias Geerinckx-Rice <me@tobias.gr>,
Maxime Devos <maximedevos@telenet.be>,
Liliana Marie Prikler <liliana.prikler@gmail.com>
Subject: [bug#55606] [PATCH 2/2] gnu: Add hare.
Date: Sun, 26 Jun 2022 00:40:45 -0400 [thread overview]
Message-ID: <87v8so81lg.fsf@mailbox.org> (raw)
In-Reply-To: <CKZESLZJRMLX.MJV2YNDL09F9@guix-aspire>
Hi (,
"(" <paren@disroot.org> writes:
> Some notes:
>
> + `hare` is not a compiler for Hare, it's a build tool. (It's going to
> include a self-hosted compiler eventually though :))
The above 2 patches are a combination of your guixrus patches and mine.
The descriptions are replaced with your better ones, and you are
credited at the top.
> + I think the way this patch handles config.mk from `hare` is better.
I kept that part in the new patches.
> + The Guix 'R Us version works with cross-compilation; I don't think this
> one does?
You mean cross-compilation of hare code? When I try to use hare build -t
(the target flag) it gives me a not implemented error, so I don't think
hare cross-compilation is possible right now.
As for cross-compilation of the guix hare build, I think the
platform-linux-architecture bit should take care of it, right?
> + harec and qbe probably shouldn't be propagated; their paths should be
> patched into the source code.
>
> -- (
I'm unsure about this one - maybe the user would want to use harec or
qbe by themselves to debug a build step?
I wanted to give the user a full hare build environment when
they run `guix install hare`, but I understand your logic for wanting to
patch the paths in.
Thanks,
Antero
next prev parent reply other threads:[~2022-06-26 4:57 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 1:21 [bug#55605] [PATCH 1/2] gnu: Add qbe Antero Mejr via Guix-patches via
2022-05-24 1:21 ` [bug#55606] [PATCH 2/2] gnu: Add hare Antero Mejr via Guix-patches via
2022-05-24 17:01 ` Maxime Devos
2022-05-24 17:07 ` Maxime Devos
2022-05-24 17:09 ` Maxime Devos
2022-05-24 17:10 ` Tobias Geerinckx-Rice via Guix-patches via
2022-05-29 0:54 ` [bug#55606] [PATCH] " Antero Mejr via Guix-patches via
2022-06-03 17:54 ` [bug#55606] Antero Mejr via Guix-patches via
2022-06-25 16:54 ` [bug#55606] [PATCH 2/2] gnu: Add hare Liliana Marie Prikler
2022-06-25 17:53 ` ( via Guix-patches via
2022-06-26 4:56 ` Antero Mejr via Guix-patches via
2022-06-25 17:59 ` ( via Guix-patches via
2022-06-26 4:40 ` Antero Mejr via Guix-patches via [this message]
2022-06-26 7:30 ` Maxime Devos
2022-06-26 7:34 ` Maxime Devos
2022-06-26 10:58 ` ( via Guix-patches via
2022-06-26 14:07 ` Antero Mejr via Guix-patches via
2022-06-26 14:27 ` Maxime Devos
2022-06-26 14:39 ` Antero Mejr via Guix-patches via
2022-07-24 16:10 ` ( via Guix-patches via
2022-06-25 21:32 ` Antero Mejr via Guix-patches via
2022-06-26 4:39 ` [bug#55606] [PATCH 1/2] gnu: Add harec Antero Mejr via Guix-patches via
2022-06-26 4:39 ` [bug#55606] [PATCH 2/2] gnu: Add hare Antero Mejr via Guix-patches via
2022-06-26 7:18 ` Liliana Marie Prikler
2022-06-26 11:05 ` ( via Guix-patches via
2022-06-26 14:00 ` Antero Mejr via Guix-patches via
2022-06-26 6:50 ` [bug#55606] [PATCH 1/2] gnu: Add harec Liliana Marie Prikler
2022-06-26 13:59 ` Antero Mejr via Guix-patches via
2022-06-26 13:59 ` [bug#55606] [PATCH 2/2] gnu: Add hare Antero Mejr via Guix-patches via
2022-06-26 14:20 ` Maxime Devos
2022-06-26 14:30 ` Antero Mejr via Guix-patches via
2022-06-26 14:39 ` Maxime Devos
2022-06-26 14:22 ` Maxime Devos
2022-06-26 14:33 ` Antero Mejr via Guix-patches via
2022-06-26 14:44 ` Maxime Devos
2022-06-26 14:53 ` Maxime Devos
2022-05-24 16:56 ` [bug#55605] [PATCH 1/2] gnu: Add qbe Maxime Devos
2022-05-24 21:06 ` Maxime Devos
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=87v8so81lg.fsf@mailbox.org \
--to=guix-patches@gnu.org \
--cc=55606@debbugs.gnu.org \
--cc=antero@mailbox.org \
--cc=liliana.prikler@gmail.com \
--cc=maximedevos@telenet.be \
--cc=me@tobias.gr \
--cc=paren@disroot.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.
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.