From: Maxime Devos <maximedevos@telenet.be>
To: muradm <mail@muradm.net>, 56136@debbugs.gnu.org
Cc: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
Subject: [bug#56136] [PATCH] gnu: freedesktop: Add basu 0.2.0.
Date: Wed, 22 Jun 2022 13:54:28 +0200 [thread overview]
Message-ID: <6de426083100110524ba722152e898d82ff083b7.camel@telenet.be> (raw)
In-Reply-To: <20220622084035.10863-1-mail@muradm.net>
[-- Attachment #1: Type: text/plain, Size: 711 bytes --]
muradm schreef op wo 22-06-2022 om 11:40 [+0300]:
> + (inputs
> + (list pkg-config python gperf libcap))
(Didn't notice this previously):
* gperf is a binary (usually) run during the build to generate stuff,
so it needs to be in native-inputs for cross-compilation to work.
* pkg-config is almost surely needs to be native-inputs (it's like a
(cross-) compiler). "./pre-inst-env guix lint basu" probably would
report this.
As a test, you can try
"./pre-inst-env guix build basu --target=aarch64-linux-gnu" or
such.
* whether python is native- or non-native depends on how it is used.
* libcap looks fine from here.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-06-22 11:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 8:40 [bug#56136] [PATCH] gnu: freedesktop: Add basu 0.2.0 muradm
2022-06-22 10:02 ` Maxime Devos
2022-06-22 10:32 ` [bug#56136] [PATCH v2] " muradm
2022-06-22 11:54 ` Maxime Devos [this message]
2022-06-22 12:00 ` [bug#56136] [PATCH v3] " muradm
2022-06-22 12:07 ` [bug#56136] [PATCH] " muradm
2022-06-22 13:08 ` Maxime Devos
2022-06-22 13:14 ` muradm
2022-06-22 13:21 ` [bug#56136] [PATCH v4] " muradm
2022-06-22 19:36 ` bug#56136: " Liliana Marie Prikler
2022-06-22 16:32 ` [bug#56136] [PATCH] " 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
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=6de426083100110524ba722152e898d82ff083b7.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=56136@debbugs.gnu.org \
--cc=liliana.prikler@ist.tugraz.at \
--cc=mail@muradm.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).