unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Manolis Ragkousis <manolis837@gmail.com>
Cc: Guix-devel <Guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: cross-base: Add libc/hurd.
Date: Thu, 30 Oct 2014 00:04:47 +0100	[thread overview]
Message-ID: <87ppdaeauo.fsf@gnu.org> (raw)
In-Reply-To: <CAFtzXzN6bHGr4L-iCqZUDU8onHpTV2hEwEuGa5U-fop0mGoJ=w@mail.gmail.com> (Manolis Ragkousis's message of "Sun, 26 Oct 2014 10:27:04 +0000")

Manolis Ragkousis <manolis837@gmail.com> skribis:

> From 66df601071d093c5532dec4c1ff55beb141a53d1 Mon Sep 17 00:00:00 2001
> From: Manolis Ragkousis <manolis837@gmail.com>
> Date: Sun, 26 Oct 2014 11:29:41 +0000
> Subject: [PATCH] gnu: cross-base: Add libc/hurd.
>
> * gnu/packages/cross-base.scm (cross-libc/hurd): New variable.

Apologies for the loooong delay again!

I’ve applied it locally on wip-hurd, but we’re missing a bit I think:

--8<---------------cut here---------------start------------->8---
$ ./pre-inst-env guix build -e '((@@ (gnu packages cross-base) cross-libc/hurd) "i686-gnu")'
[...]
ERROR: dynamic linker name not known for this system "i686-gnu"
--8<---------------cut here---------------end--------------->8---

Or did you test it differently?

It’s a great start, but I wonder how we could eventually reduce
duplication between ‘cross-libc’ and ‘cross-libc/hurd’.

Thanks,
Ludo’.

  reply	other threads:[~2014-10-29 23:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-26 10:27 [PATCH] gnu: cross-base: Add libc/hurd Manolis Ragkousis
2014-10-29 23:04 ` Ludovic Courtès [this message]
2014-11-01  9:44   ` Manolis Ragkousis
2014-11-09 10:41     ` Manolis Ragkousis
2014-11-19 10:26       ` Ludovic Courtès
2014-11-30 19:01         ` Manolis Ragkousis
2014-11-30 22:31           ` Ludovic Courtès
2014-12-01 22:43             ` Manolis Ragkousis
2014-12-06 22:21               ` Ludovic Courtès
2014-12-06 22:53                 ` Manolis Ragkousis
2014-12-07 20:27                   ` Ludovic Courtès
2014-11-19 10:20     ` 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

  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=87ppdaeauo.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=Guix-devel@gnu.org \
    --cc=manolis837@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).