all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 43950-done@debbugs.gnu.org
Subject: bug#43950: lz4 CC=gcc - Why?
Date: Mon, 12 Oct 2020 20:03:40 +0200	[thread overview]
Message-ID: <875z7fiao3.fsf@nckx> (raw)
In-Reply-To: <20201012155701.54fa6bae@scratchpost.org>

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

Hi Danny,

Danny Milosavljevic 写道:
> It's a dependency of genimage (via squashfs-tools).  Breaking it 
> breaks
> guix system image generation.
>
> It's a dependency of u-boot.  Breaking it breaks booting on all 
> ARM
> machines.

Thanks.  Yes, unfortunately it's a dependency of a lot, making it 
a staging package.

I didn't rebuild all dependents before pushing but I did build 
several packages including u-boot-pine64-lts (on x86_64) as a 
smoke test.  I also verified that lz4 with 
--target=aarch64-linux-gnu actually builds for aarch64 now.  I 
think it's safe.

If anything were to break I'd say it must have been broken before, 
but do let me know if it happens.

> Ludo said to send extra mails for each--so that's what I am 
> doing.

Each package using CC=gcc?  There are currently hundreds; I don't 
think that's what Ludo' meant.  Do hope to have it down to tens 
soon...

Kind regards,

T G-R

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

      reply	other threads:[~2020-10-12 18:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-12 12:21 bug#43950: lz4 CC=gcc - Why? Danny Milosavljevic
2020-10-12 13:18 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-10-12 13:57   ` Danny Milosavljevic
2020-10-12 18:03     ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875z7fiao3.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=43950-done@debbugs.gnu.org \
    --cc=dannym@scratchpost.org \
    --cc=me@tobias.gr \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.