all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Manolis Ragkousis <manolis837@gmail.com>
Cc: Guix-devel@gnu.org
Subject: Re: Fwd: [PATCH] gnu: hurd: Add Hurd Minimal.
Date: Mon, 26 May 2014 11:22:18 +0200	[thread overview]
Message-ID: <877g58rj1x.fsf@gnu.org> (raw)
In-Reply-To: <CAFtzXzPVtxrVV_7uR4CBH+AHL5d-dQtKUYx0=B7K5Vn2Cp9r8A@mail.gmail.com> (Manolis Ragkousis's message of "Mon, 26 May 2014 08:24:54 +0000")

Manolis Ragkousis <manolis837@gmail.com> skribis:

>>> +    (arguments
>>> +     `(#:out-of-source? #t
>>> +       #:phases (alist-replace
>>> +                 'install
>>> +                 (lambda* (#:key outputs #:allow-other-keys)
>>> +                   (let ((out (assoc-ref outputs "out")))
>>> +                     ;; We need to copy libihash.a to the output folder manually,
>>> +                     ;; since there is no target for that in the makefile
>>> +                     (copy-recursively "libihash"
>>> +                                       (string-append out "/libihash"))
>>
>> This creates
>> /gnu/store/.../libihash/{libihash.a,Makefile,ihash.c,ihash.o,...}.  Is
>> it really what’d intended?
>>
>> I would expect that the intent is to create
>> /gnu/store/.../{lib/libihash.a,include/ihash.h}, no?
>>
> I will create two folders, lib with libihash.a and include with
> ihash.h. What do you think?

Yes, that’s what I’d expect.  Double-check to make sure ihash.h doesn’t
include any other file that’d need to be installed.

(Please use “directory” rather than “folder” in comments & co.)

>>> ++if test "x$cross_compiling" = "xyes"; then
>>> ++   # It may be that we don't have a working libc yet, for instance
>>> ++   # because we're bootstrapping the cross-compilation tool chain.
>>> ++   # Thus, use this undocumented Autoconf macro designed for this.
>>> ++   AC_NO_EXECUTABLES
>>> ++   echo done
>>> ++fi
>>
>> I gather that this works as advertised, but could you confirm by
>> replying to
>> <http://lists.gnu.org/archive/html/bug-hurd/2014-04/msg00139.html>?
>> That would allow us to push the patch upstream.
>>
>
> I had to put one more line after AC_NO_EXECUTABLES, otherwise it would fail with
>> syntax error near unexpected token `fi'.

Oh I see, this macro actually expands to nothing.

> Other than that it works. I will confirm there.

Thanks.

>>> +-# Check for Sun RPC headers and library.
>>> ++# Check only for Sun RPC headers. We do not need the library yet.
>>> + AC_CHECK_HEADER([rpc/types.h], [HAVE_SUN_RPC=yes], [HAVE_SUN_RPC=no])
>>> +-AC_SEARCH_LIBS([clnt_create], [], [:], [HAVE_SUN_RPC=no])
>>> ++# AC_SEARCH_LIBS([clnt_create], [], [:], [HAVE_SUN_RPC=no])
>>> + AC_SUBST([HAVE_SUN_RPC])
>>
>> What’s the problem that’s addressed here?
>
> It tries to link with a library in glibc (which at that point doesn't
> yet exist ),
> but it cant because of the AC_NO_EXECUTABLES flag saying that linking
> is not allowed after this flag is passed. So I am just disabling the test, to
> get the job done.

OK, I see.  Make sure to mention it in the patch comment as well.

Ludo’.

  reply	other threads:[~2014-05-26  9:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-24 19:57 [PATCH] gnu: hurd: Add Hurd Minimal Manolis Ragkousis
2014-05-24 22:05 ` Nikita Karetnikov
2014-05-24 22:42   ` Ludovic Courtès
2014-05-24 23:12 ` Ludovic Courtès
     [not found]   ` <CAFtzXzMEQnzdvSV5+6NNjEZizoRyoJf4PhBGXqXeTeu7vjU_mg@mail.gmail.com>
2014-05-26  8:24     ` Fwd: " Manolis Ragkousis
2014-05-26  9:22       ` Ludovic Courtès [this message]
2014-05-29 20:55         ` Manolis Ragkousis
2014-05-30 16:06           ` Ludovic Courtès
2014-06-01 14:45             ` Manolis Ragkousis
2014-06-01 15:20               ` Manolis Ragkousis
2014-06-01 22:00                 ` Ludovic Courtès
2014-06-02 16:28                   ` Andreas Enge
2014-06-02 16:31                     ` Manolis Ragkousis
2014-06-02 21:30                     ` 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=877g58rj1x.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 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.