all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: 宋文武 <iyzsong@gmail.com>
To: sleep_walker@suse.cz
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: missing input and more
Date: Thu, 5 Feb 2015 17:48:07 +0800	[thread overview]
Message-ID: <CAHZE2pd5cEm_3L0inm16XP3t3qdvEFJ516U30Nk4FeSgXnPUTg@mail.gmail.com> (raw)
In-Reply-To: <20150205070425.GA25300@venom>

2015-02-05 15:05 GMT+08:00  <sleep_walker@suse.cz>:
> Hi Guix,
>
> during my packaging attempts of connman (which looks good so far) I
> found that gnutls is missing "install-time" dependency - zlib.
>
> 1] ldd shows run-time dependency:
> $ ldd
> /gnu/store/0mfgwxgqyhlvi5xyi1j2lbr3ygczsdyp-gnutls-3.2.21/lib/libgnutls.so |
> grep libz
>        libz.so.1 =>
> /gnu/store/x8cg3irwf8y2mkr88bqmsqhadi71xf6s-zlib-1.2.7/lib/libz.so.1
> (0x00007fe4fac90000)
>
> 2] pkg-config rants about not filled dependencies when building against
> gnutls
>
> In
> /gnu/store/0mfgwxgqyhlvi5xyi1j2lbr3ygczsdyp-gnutls-3.2.21/lib/pkgconfig/gnutls.pc
> you can see
>
> Libs.private: -lz        -lgmp
> Requires.private: nettle, hogweed, libtasn1, zlib
>
>
> That is something which should be solved by "propagate-input"?
Yes, zlib should be a propagate-input of gnutls.
>
> Both dependency requirements types are quite easy to detect. I'm not
> sure if they shouldn't be done in package build
> (maintaining mapping for pkg-config *.pc --> package)
>
> or we should just invest time into package validation afterwards.
>
> WDYT?
>
> S_W

  reply	other threads:[~2015-02-05  9:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-05  7:05 missing input and more sleep_walker
2015-02-05  9:48 ` 宋文武 [this message]
2015-02-05 10:30 ` Andreas Enge
2015-02-05 11:01   ` 宋文武
2015-02-05 11:57     ` Tomas Cech
2015-02-05 16:01       ` Andreas Enge
2015-02-05 20:54         ` Ludovic Courtès
2015-02-05 15:59     ` 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=CAHZE2pd5cEm_3L0inm16XP3t3qdvEFJ516U30Nk4FeSgXnPUTg@mail.gmail.com \
    --to=iyzsong@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=sleep_walker@suse.cz \
    /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.