From: "Gérald Lelong" <lelong.gerald@gmail.com>
To: guix-devel@gnu.org
Subject: perl for arm-linux-gnueabihf
Date: Fri, 18 Jan 2019 15:45:55 +0100 [thread overview]
Message-ID: <CAHySp3Qip=XVVvYU=heehoaM+RD1U3AE8MBUh0iya=j0QXnzxQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 202 bytes --]
*guix build --target=arm-linux-gnueabihf* *perl* fails with the following
output: https://pastebin.com/QF0xKAmR
It looks like *libc *input evaluates to *false* for the
*remove-extra-references
*phase.
[-- Attachment #2: Type: text/html, Size: 347 bytes --]
next reply other threads:[~2019-01-18 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 14:45 Gérald Lelong [this message]
2019-01-19 9:45 ` perl for arm-linux-gnueabihf Ricardo Wurmus
2019-01-20 22:39 ` Ludovic Courtès
2020-08-11 9:01 ` bug#27149: " Jan Nieuwenhuizen
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='CAHySp3Qip=XVVvYU=heehoaM+RD1U3AE8MBUh0iya=j0QXnzxQ@mail.gmail.com' \
--to=lelong.gerald@gmail.com \
--cc=guix-devel@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).