all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: Patches for midnight commander
Date: Wed, 26 Mar 2014 14:46:27 +0100	[thread overview]
Message-ID: <87txal2hu4.fsf@gnu.org> (raw)
In-Reply-To: <87eh1pk9ql.fsf@yeeloong.lan> (Mark H. Weaver's message of "Tue, 25 Mar 2014 21:51:46 -0400")

Mark H Weaver <mhw@netris.org> skribis:

> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Eric Bavier <ericbavier@gmail.com> skribis:
>>
>>> --- a/gnu/packages/ssh.scm
>>> +++ b/gnu/packages/ssh.scm
>>> @@ -110,6 +110,18 @@ remote applications.")
>>>     (build-system gnu-build-system)
>>>     (inputs `(("libgcrypt" ,libgcrypt)
>>>               ("zlib" ,zlib)))
>>> +   (arguments
>>> +    '(#:configure-flags
>>> +      `("--with-libgcrypt"
>>> +        ;; Programs that use libssh2.pc to link against libssh2 need to also
>>> +        ;; know where to find libgrypt and zlib libraries.  LDFLAGS are put
>>> +        ;; into the LIBS field of libssh2.pc
>>> +        ,(string-append
>>> +          "LDFLAGS=-L"
>>> +          (assoc-ref %build-inputs "libgcrypt")
>>> +          "/lib -L"
>>> +          (assoc-ref %build-inputs "zlib")
>>> +          "/lib"))))
>>
>> Another way to address that would be to rename ‘inputs’ to
>> ‘native-inputs’.
>
> Did you mean to write 'propagated-inputs' here?

Yes!  Sorry.

Ludo’.

  reply	other threads:[~2014-03-26 13:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-25 21:09 Patches for midnight commander Eric Bavier
2014-03-25 22:41 ` Ludovic Courtès
2014-03-26  1:51   ` Mark H Weaver
2014-03-26 13:46     ` Ludovic Courtès [this message]
2014-03-26  1:47 ` Mark H Weaver
2014-03-26 14:20   ` Eric Bavier
2014-03-26 14:53     ` Andreas Enge

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=87txal2hu4.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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 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.