From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Progress on the Hurd; new state of wip-hurd-vm
Date: Mon, 20 Apr 2020 07:39:32 +0200 [thread overview]
Message-ID: <87d082sokr.fsf@gnu.org> (raw)
In-Reply-To: <93704715-88da-2d3b-fd51-d7bc99d6b346@gmail.com> (Vincent Legoll's message of "Sun, 19 Apr 2020 17:32:07 +0200")
Vincent Legoll writes:
Hello Vincent,
> I just had a tour of that branch, it looks like there are interesting
> patches wrt cross-building, aren't those ready for upstream (core-
> updates maybe) ?
Yes, some of them (gnutls, git, python) have just been cleaned-up and
applied to core-updates.
> I'm looking at the first one (for perl) for example...
Ah, that one took some review and effort, see https://bugs.gnu.org/40698
and has now been applied too.
> I've been trying to cross-compile the binary-tarball to new arches,
> without any success, all failing the same way, on perl...
>
> And when it hit me that there is a recurring theme in those failures
> I found a few issues and ML posts about the same problem.
>
> So, what's the status of those patches ?
Hard to tell! Some of those are ready, others need review, others need
work.
The autotools patches need review, but they work. The patches to
cross-build guix need some discussion and worse, cross-compiling guix
currently uses a terrible kludge; so while also that "works", its still
under development.
Greetings,
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2020-04-20 5:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 14:50 Progress on the Hurd; new state of wip-hurd-vm Jan Nieuwenhuizen
2020-04-19 15:32 ` Vincent Legoll
2020-04-20 5:39 ` Jan Nieuwenhuizen [this message]
2020-04-20 7:50 ` Vincent Legoll
2020-04-22 7:35 ` 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=87d082sokr.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=guix-devel@gnu.org \
--cc=vincent.legoll@gmail.com \
/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).