From: Maxime Devos <maximedevos@telenet.be>
To: 47006@debbugs.gnu.org
Subject: [bug#47006] [PATCH] gnu: Add zig.
Date: Sun, 11 Apr 2021 23:04:15 +0200 [thread overview]
Message-ID: <8937efa5c022c9791a0402cf561384057b29bc77.camel@telenet.be> (raw)
In-Reply-To: <20210308131155.7441-1-leo.prikler@student.tugraz.at>
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
One comment below.
> + (native-inputs
> + `(("clang" ,clang-11)
> + ("lld" ,lld)
> + ("llvm" ,llvm-11)))
This looks rather suspicious from a cross-compilation perspective.
IIUC, lld and llvm are used for two purposes:
* for compiling the "zig" compiler --> native-inputs is ok
(or is GCC used to compile the zig compiler?)
* as a run-time dependency of "zig" --> should be 'inputs'
Therefore, shouldn't "lld" and "llvm" be added to "inputs" as well?
TODO to self: define a variant of disallowed-references
disallowed-references/native that refers to the package in 'native-inputs'
instead of 'inputs'.
Perhaps explicitely whitelist some inputs (llvm, lld, maybe some implicit
libc inputs?).
Note: according to me, *all* inputs in native-inputs should be added
to disallowed-references *by default* when cross-compiling.
Alternatively, I guess ‘we’ could simply add a comment
;; Cross-compilation is currently unsupported.
and leave cross-compilation for later. My comments are mostly about
‘giving the good example’ on how to use inputs & native-inputs and avoid
giving ‘bad examples’ of package definitions without marking them as such.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2021-04-11 21:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 13:11 [bug#47006] [PATCH] gnu: Add zig Leo Prikler
2021-03-15 14:20 ` [bug#47006] [PATCH v2 0/1] " Léo Le Bouter via Guix-patches via
2021-03-15 14:20 ` [bug#47006] [PATCH v2 1/1] " Léo Le Bouter via Guix-patches via
2021-03-16 12:57 ` [bug#47006] [PATCH] " Efraim Flashner
2021-03-16 13:09 ` Leo Prikler
2021-03-17 7:05 ` Léo Le Bouter via Guix-patches via
2021-04-09 22:17 ` [bug#47006] (No Subject) terramorpha--- via Guix-patches via
2021-04-11 21:04 ` Maxime Devos [this message]
2021-05-30 9:32 ` [bug#47006] Zig question Sharlatan Hellseher
2021-09-11 0:01 ` [bug#47006] [PATCH] gnu: Add zig András Vöröskői
2021-09-11 18:45 ` András Vöröskői
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=8937efa5c022c9791a0402cf561384057b29bc77.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=47006@debbugs.gnu.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 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).