From: Maxime Devos <maximedevos@telenet.be>
To: "Paul A. Patience" <paul@apatience.com>, 56638@debbugs.gnu.org
Subject: [bug#56638] [PATCH] gnu: Add asli.
Date: Tue, 19 Jul 2022 16:32:27 +0200 [thread overview]
Message-ID: <32bcb714d63fcc1a7258d28d1a4c7d8f3fcc3995.camel@telenet.be> (raw)
In-Reply-To: <20220719075934.67481-1-paul@apatience.com>
Paul A. Patience schreef op di 19-07-2022 om 07:59 [+0000]:
> + (native-inputs
> + ;; Header-only library
> + (list cgal))
Being header-only makes no difference w.r.t. cross-compilation (and
hence, inputs/native-inputs). For examples, headers can potentially
contain architecture-specific code (generated at the compile time of
the cgal library). As such, this may need to be in 'inputs' instead of
'native-inputs'.
Another reason: this should be in 'inputs', otherwise when cross-
compiling it will end in in (IIUC) C_INCLUDE_PATH instead of
CROSS_C_INLUDE_PATH, whereas the cross-compiler will look in
CROSS_C_INCLUDE_PATH and not C_INCLUDE_PATH.
Greetings,
Maxime.
next prev parent reply other threads:[~2022-07-19 14:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 7:59 [bug#56638] [PATCH] gnu: Add asli Paul A. Patience
2022-07-19 8:10 ` Paul A. Patience
2022-07-19 14:21 ` Ludovic Courtès
2022-07-19 14:32 ` Maxime Devos [this message]
2022-07-19 14:34 ` Maxime Devos
2022-07-24 12:02 ` [bug#56638] [PATCH v2 0/2] " Paul A. Patience
2022-07-24 12:02 ` [bug#56638] [PATCH v2 1/2] gnu: Add mmg Paul A. Patience
2022-08-29 21:21 ` [bug#56638] [PATCH] gnu: Add asli Ludovic Courtès
2022-07-24 12:02 ` [bug#56638] [PATCH v2 2/2] " Paul A. Patience
2022-08-04 21:40 ` [bug#56638] [PATCH] " Ludovic Courtès
2022-08-29 21:21 ` Ludovic Courtès
2022-08-30 12:01 ` Paul A. Patience
2022-09-02 20:34 ` [bug#56638] [PATCH v3] " Paul A. Patience
2022-09-13 19:02 ` Paul A. Patience
2022-09-14 21:13 ` [bug#56638] [PATCH] " Ludovic Courtès
2022-09-15 13:37 ` Paul A. Patience
2023-06-20 0:39 ` Paul A. Patience
2023-09-08 17:16 ` bug#56638: " Ludovic Courtès
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=32bcb714d63fcc1a7258d28d1a4c7d8f3fcc3995.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=56638@debbugs.gnu.org \
--cc=paul@apatience.com \
/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).