guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 1/4] gnu: base: Add glibc-hurd and hurd-minimal.


From: Manolis Ragkousis
Subject: Re: [PATCH 1/4] gnu: base: Add glibc-hurd and hurd-minimal.
Date: Wed, 18 Feb 2015 11:37:28 +0200

> After a few iterations on IRC, I proposed this code which seems to work:
>
> --8<---------------cut here---------------start------------->8---
>        ((#:configure-flags original-configure-flags)
>         `(append (list "--host=i686-pc-gnu"
>
>                        ;; nscd fails to build for GNU/Hurd:
>                        ;; 
> <https://lists.gnu.org/archive/html/bug-hurd/2014-07/msg00006.html>.
>                        ;; Disable it.
>                        "--disable-nscd")
>                  (filter (lambda (flag)
>                            (not (or (string-prefix? "--with-headers=" flag)
>                                     (string-prefix? "--enable-kernel=" 
> flag))))
>                          ;; Evaluate 'original-configure-flags' in a
>                          ;; lexical environment that has a dummy
>                          ;; "linux-headers" input, to prevent errors.
>                          (let ((%build-inputs `(("linux-headers" "@DUMMY@")
>                                                 ,@%build-inputs)))
>                            ,original-configure-flags))))
> --8<---------------cut here---------------end--------------->8---

The above code works perfectly. Mark I added you as a co-author to this patch
because your help was invaluable. Thank you :-)

> but obviously it's a bit gross.  Ideally, we consider consider having a
> 'glibc/base' package that is inherited by both 'glibc/linux' and
> 'glibc/hurd'.  The base package would not add any linux stuff, on the
> theory that it is easier and cleaner to add kernel-specific stuff than
> to remove it.

The best solution would have been to have a single glibc package for
everything but as
this is not possible with the current status of the hurd glibc, I
believe your idea
would really help avoid any futute problems and help simplify everything.
Then we would just have a simple macro in base.scm that would choose the right
glibc depending on the target/current system. Can/will do and update
you on this.

But for now the current solution will do in order to continue working
on the port.
Here is the updated patch after Mark's suggestions.

Attachment: 0001-gnu-base-Add-glibc-hurd-and-hurd-minimal.patch
Description: Text Data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]