all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: 43986@debbugs.gnu.org
Subject: bug#43986: core-updates' grep and coreutils fail strerror_r and perror2 tests in gnulib-tests on armhf-on-aarch64
Date: Wed, 21 Oct 2020 18:04:16 +0200	[thread overview]
Message-ID: <20201020190151.38ad32f1@scratchpost.org> (raw)
In-Reply-To: <20201020092246.5a27c998@scratchpost.org>

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

and sed, while trying to prepare the guix environment for grep.

and gettext-minimal 0.21, while trying to prepare the guix environment for grep.

Happens both with this: guix environment -s armhf-linux --pure grep
And with this: guix environment -s armhf-linux --pure -e '(@@ (gnu packages commencement) grep-final)'
That's BEFORE successfully entering the environment.

After fixing all of those, I'm finally in a guix environment for grep.

To be clear, for each of my messages in this bug report, I've made sure to try
it on unmodified core-updates--and it totally fails there, too.

I've not updated from core-updates origin since a few days ago since I don't
want to build all the derivations again.  So Ludo's update of grep to 3.5
I have not seen yet (it's grep 3.4 right now).

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-10-21 16:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-14 10:41 bug#43986: core-updates' grep and coreutils fail strerror_r and perror2 tests in gnulib-tests on armhf-on-aarch64 Danny Milosavljevic
2020-10-17 10:20 ` Danny Milosavljevic
2020-10-17 18:59   ` bokr
2020-10-18 22:45   ` Danny Milosavljevic
2020-10-20  7:22     ` Danny Milosavljevic
2020-10-21 16:04       ` Danny Milosavljevic [this message]
2020-10-21 17:03         ` Danny Milosavljevic
2020-10-18 22:49   ` Marius Bakke
2020-10-21 10:26     ` 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

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

  git send-email \
    --in-reply-to=20201020190151.38ad32f1@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=43986@debbugs.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 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.