From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: jgart <jgart@dismail.de>, 53833@debbugs.gnu.org
Subject: [bug#53833] [PATCH] gnu: Add qbe.
Date: Mon, 07 Feb 2022 10:47:08 +0100 [thread overview]
Message-ID: <7974e4fbf6a2b7beb41ead69a708a78a460b295e.camel@ist.tugraz.at> (raw)
In-Reply-To: <20220207011332.27844-1-jgart@dismail.de>
Am Sonntag, dem 06.02.2022 um 20:13 -0500 schrieb jgart:
> * gnu/packages/c.scm (qbe): New variable.
> ---
> gnu/packages/c.scm | 30 ++++++++++++++++++++++++++++++
> 1 file changed, 30 insertions(+)
>
> diff --git a/gnu/packages/c.scm b/gnu/packages/c.scm
> index 459d996fa2..8966b7b8d0 100644
> --- a/gnu/packages/c.scm
> +++ b/gnu/packages/c.scm
> @@ -142,6 +142,36 @@ (define-public pcc
> ;; preferred. See http://pcc.ludd.ltu.se/licenses/ for more
> details.
> (license (list license:bsd-2 license:bsd-3))))
>
> +(define-public qbe
> + (let ((commit "2ca6fb25a238842418019a3f9ee8d1beb1327f7e")
> + (revision "0"))
> + (package
> + (name "qbe")
> + (version (git-version "0.0" revision commit))
From the homepage: "QBE is in constant change. It is a young project
and I still have many ideas to try." As always, I don't think it's too
good of an idea to package projects that tell you "this edge will make
you bleed". Or in the words of the manual
> Occasionally, we package snapshots of upstream’s version control
> system (VCS) instead of formal releases. This should remain
> exceptional, because it is up to upstream developers to clarify what
> the stable release is.
I think upstream is very clear here that QBE is not yet stable and
therefore not something you'd want in a distro. Of course, since the
recipe is a rather simple one, you can easily maintain it in your own
channel -- or not package it at all and use it from source with just a
C compiler.
> + (source
> + (origin
> + (method git-fetch)
> + (uri
> + (git-reference
> + (url "git://c9x.me/qbe")
> + (commit commit)))
> + (file-name (git-file-name name version))
> + (sha256
> + (base32
> +
> "0qbnsrwk10v0s42vzxy2wvksd8xl8bmxfzqv2a4j4zjaklqgfd6j"))))
> + (build-system gnu-build-system)
> + (arguments
> + `(#:tests? #f ; Tests require a running qemu?
You should be able to add qemu to native-inputs if that's all it takes.
> + #:make-flags (list (string-append "CC=" ,(cc-for-target))
> + (string-append "PREFIX=" %output))
> + #:phases
> + (modify-phases %standard-phases
> + (delete 'configure))))
> + (synopsis "Backend compiler")
> + (description "@code{qbe} is a compiler backend.")
It'd be nice if the description was more descriptive :)
Also the synopsis should probably not invert the ordering of "compiler"
and "backend".
> + (home-page "https://c9x.me/compile/")
> + (license license:expat))))
> +
> (define-public libbytesize
> (package
> (name "libbytesize")
Cheers
next prev parent reply other threads:[~2022-02-07 10:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 1:13 [bug#53833] [PATCH] gnu: Add qbe jgart via Guix-patches via
2022-02-07 9:47 ` Liliana Marie Prikler [this message]
2022-02-08 21:10 ` jgart via Guix-patches via
2022-04-05 16:11 ` bug#53833: " Ludovic Courtès
2022-04-25 20:08 ` [bug#53833] " paren--- via Guix-patches via
2022-04-26 18:16 ` paren--- via Guix-patches via
2022-05-07 16:34 ` [bug#53833] QBE and cproc upstreaming paren--- via Guix-patches via
2022-05-07 17:09 ` [bug#53833] [PATCH] gnu: Add qbe (unmatched-parenthesis via Guix-patches via
2022-05-07 17:11 ` [bug#53833] [PATCH] gnu: patches: Add qbe-makefile-add-target.patch (unmatched-parenthesis via Guix-patches via
2022-05-07 17:21 ` [bug#53833] [PATCH] gnu: packages: c: Add (unmatched parenthesis copyright statement (unmatched-parenthesis via Guix-patches via
2022-05-07 18:19 ` [bug#53833] Upstreaming QBE and cproc paren--- via Guix-patches via
2022-05-08 20:21 ` [bug#53833] [PATCH v2] gnu: Add qbe (unmatched-parenthesis via Guix-patches via
2022-05-24 6:50 ` Liliana Marie Prikler
2022-05-24 19:44 ` bug#53833: " Liliana Marie Prikler
[not found] <454d4c514fc4485670cf8f2ec891034c9014edc0@disroot.org>
2022-04-26 7:43 ` [bug#53833] [PATCH] " Liliana Marie Prikler
2022-05-01 13:16 ` Ludovic Courtès
2022-05-02 6:33 ` Liliana Marie Prikler
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=7974e4fbf6a2b7beb41ead69a708a78a460b295e.camel@ist.tugraz.at \
--to=liliana.prikler@ist.tugraz.at \
--cc=53833@debbugs.gnu.org \
--cc=jgart@dismail.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.