All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Westerhof <mike@mwester.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] vsftpd-2.0.5: added dependency for correct build order
Date: Fri, 11 Mar 2011 14:32:43 -0600	[thread overview]
Message-ID: <4D7A86EB.2090504@mwester.net> (raw)
In-Reply-To: <201103101553.27407.pgsellmann@portner-elektronik.at>

On 3/10/2011 8:53 AM, Peter Gsellmann wrote:
> vsftpd needs the cap_* functions; if the library libcap is not built before vsftpd, an error occurs.
> 
> Signed-off-by: Peter Gsellmann <pgsellmann@portner-elektronik.at>
> ---
>  recipes/vsftpd/vsftpd_2.0.5.bb |    4 +++-
>  1 files changed, 3 insertions(+), 1 deletions(-)
> 
> diff --git a/recipes/vsftpd/vsftpd_2.0.5.bb b/recipes/vsftpd/vsftpd_2.0.5.bb
> index 518628e..2486744 100644
> --- a/recipes/vsftpd/vsftpd_2.0.5.bb
> +++ b/recipes/vsftpd/vsftpd_2.0.5.bb
> @@ -3,6 +3,8 @@ SECTION = "console/network"
>  LICENSE = "GPL"
>  PR = "r2"

Technically, you'll want to bump the PR as well (although for this
particular change, it'll actually work without it)


> +DEPENDS = "libcap"
> +
>  SRC_URI = "ftp://vsftpd.beasts.org/users/cevans/vsftpd-${PV}.tar.gz \
>             file://makefile.patch \
>             file://nopam.patch \
> @@ -20,7 +22,7 @@ do_configure() {
>  }
>  
>  do_compile() {
> -        oe_runmake "LIBS=-lcrypt -L${STAGING_LIBDIR}"
> +        oe_runmake "LIBS=-L${STAGING_LIBDIR} -lcrypt -lcap"
>  }
>  
>  do_install() {




  reply	other threads:[~2011-03-11 20:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-10 14:53 [PATCH] vsftpd-2.0.5: added dependency for correct build order Peter Gsellmann
2011-03-11 20:32 ` Mike Westerhof [this message]
2011-03-11 23:55   ` Khem Raj

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=4D7A86EB.2090504@mwester.net \
    --to=mike@mwester.net \
    --cc=openembedded-devel@lists.openembedded.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.
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.