unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Jean-Baptiste Note <jean-baptiste.note@m4x.org>
Cc: othacehe@gnu.org, 41150@debbugs.gnu.org
Subject: [bug#41150] [PATCH] gnu: Add powerstat.
Date: Sat, 09 May 2020 23:04:08 +0200	[thread overview]
Message-ID: <873688q0qf.fsf@nckx> (raw)
In-Reply-To: <875zd47u57.fsf@m4x.org>

[-- Attachment #1: Type: text/plain, Size: 1528 bytes --]

Jean-Baptiste!

Jean-Baptiste Note 写道:
> There are actually more than 300 such instances

*Hundreds*! :-p

On a positive note there are 3 fewer occurences on c-u (308) than 
master (311).

I used a simple ‘grep CC=gcc | wc -l’; I suspect you did something 
similar.

> and counting...

It shouldn't increase if people posts their patches for review 
(...and they actually get reviewed...).  CC=gcc is an old habit 
but not difficult to break.

> Couldn't we get a "magic" variable %target-cc like we have
> %output, %outputs -- then we could just stubstitute gcc for this
> variable...

I'm (not yet?) (no longer?) convinced that's a good idea once 
gnu-build-system takes care of those 308 packages and we're left 
with the exceptions.

When I replied to Mathieu's last mail I hadn't looked at the code 
yet:

  (let ((target ,(%current-target-system)))
    (list (string-append "CC=" (if target
                                   (string-append target "-gcc")
                                   "gcc"))))

To me, abstracting that is beyond overkill.

However, I don't know much about cross-compiling.  TBH I'd be 
sowewhat surprised if none of the CROSS-* procedures I regularly 
scroll past do something like this already.

> I would do it, if I only knew where these are defined, but my 
> scheme
> skills are definitely lacking :)

Mainly (gnu packages cross-base).

Kind regards,

T G-R, currently building kernels to properly answer your 
hibernation mails...

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2020-05-09 21:04 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
2020-05-09 20:03     ` Jean-Baptiste Note
2020-05-09 21:04       ` Tobias Geerinckx-Rice via Guix-patches via [this message]
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=873688q0qf.fsf@nckx \
    --to=guix-patches@gnu.org \
    --cc=41150@debbugs.gnu.org \
    --cc=jean-baptiste.note@m4x.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).