From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 41150@debbugs.gnu.org
Subject: [bug#41150] [PATCH] gnu: Add powerstat.
Date: Sat, 09 May 2020 19:32:15 +0200 [thread overview]
Message-ID: <87ftc9ovz4.fsf@nckx> (raw)
In-Reply-To: <87y2q1yrd7.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
Mathieu,
Mathieu Othacehe 写道:
> Hard-coding CC this way will prevent cross-compilation. You can
> have a
> look to "crda" or "libaio" for examples.
Eh? This is the first time anyone's ever mentioned that. Thanks!
It's obvious how much cross-compilation means to me.
(You realise there are *hundreds* of CC=gcc lines in current Guix,
right?)
Don't get me wrong: I love that Guix still cares so much about
cross-compilation, and the tremendous effort I see in the logs
every month to make it work better, when (at least a few years
ago) it was all the rage to declare it dead since VMs exist or
something.
> As this is a recurring pattern, we should find a way to add it
> somewhere
> in the build-system. But for now, the ugly snippet appending
> target
> should work :).
I agree that handling (only) standard GNU variables[0] in the GNU
build system makes sense.
I'll add the snippet of power.
Kind regards,
T G-R
[0]:
https://www.gnu.org/prep/standards/standards.html#Utilities-in-Makefiles
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-05-09 17:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 15:15 [bug#41150] [PATCH] gnu: Add powerstat Tobias Geerinckx-Rice via Guix-patches via
2020-05-09 17:01 ` Mathieu Othacehe
2020-05-09 17:32 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2020-05-09 20:03 ` Jean-Baptiste Note
2020-05-09 21:04 ` Tobias Geerinckx-Rice via Guix-patches via
2020-05-09 21:10 ` Tobias Geerinckx-Rice via Guix-patches via
2020-05-09 20:42 ` bug#41150: " Tobias Geerinckx-Rice via Guix-patches via
2020-05-10 7:24 ` [bug#41150] " Mathieu Othacehe
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=87ftc9ovz4.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=41150@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=othacehe@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).