Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Joe MacDonald <Joe.MacDonald@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-networking] [PATCH] autofs: fails to compile with openldap disabled
Date: Thu, 24 Jan 2013 10:42:24 -0500	[thread overview]
Message-ID: <20130124154223.GH3496@windriver.com> (raw)
In-Reply-To: <20130122151153.GA24789@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 2054 bytes --]

[Re: [oe] [meta-networking] [PATCH] autofs: fails to compile with openldap disabled] On 13.01.22 (Tue 10:11) Amy Fong wrote:

> On Mon, Jan 21, 2013 at 02:58:39PM -0500, Joe MacDonald wrote:
> Hi Joe,
> 
> > Hey Amy,
> > 
> > [[oe] [meta-networking] [PATCH] autofs: fails to compile with openldap disabled] On 13.01.18 (Fri 12:13) Amy Fong wrote:
> > 
> > > commit 09947d772a36e4d2c2dc48356281bd3ce0a04b0c
> > > Author: Amy Fong <amy.fong@windriver.com>
> > > Date:   Fri Jan 18 11:10:35 2013 -0500
> > > 
> > >     autofs: fails to compile with openldap disabled
> > >     
> > >     As of 5.0.6, it appears that changes were introduced so that
> > >     if you compile with openldap disabled and openldap headers are not
> > >     available, then autofs fails to build.
> > >     
> > >     Since autofs no longer depends on openldap, remove the dependency
> > >     
> > >     Signed-off-by: Amy Fong <amy.fong@windriver.com>
> > > 
> > > diff --git a/recipes-daemons/autofs/autofs-5.0.7/fix_disable_ldap.patch b/recipes-daemons/autofs/autofs-5.0.7/fix_disable_ldap.patch
> > > new file mode 100644
> > > index 0000000..b62f955
> > > --- /dev/null
> > > +++ b/recipes-daemons/autofs/autofs-5.0.7/fix_disable_ldap.patch
> > > @@ -0,0 +1,40 @@
> > > +autofs: fails to compile with openldap disabled
> > > +
> > > +As of 5.0.6, it appears that changes were introduced so that 
> > > +if you compile with openldap disabled and openldap headers are not
> > > +available, then autofs fails to build.
> > > +
> > > +Signed-off-by: Amy Fong <amy.fong@windriver.com>
> > 
> > Did you say you'd already sent this upstream?  I can put in an
> > upstream-status myself, but I'm not sure what it is right now.  :-)
> > 
> > Alternatively, a new version with the upstream-status is good too.
> > 
> > -J.
> 
> Nope, it wasn't sent upstream. I'd say that the upstream-status should be pending. :)

Okay, merged.  Can you ensure it gets sent up-stream since you authored
it?

Thanks Amy.

-- 
-Joe MacDonald.
:wq

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

      reply	other threads:[~2013-01-24 15:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 17:13 [meta-networking] [PATCH] autofs: fails to compile with openldap disabled Amy Fong
2013-01-21 19:58 ` Joe MacDonald
2013-01-22 15:11   ` Amy Fong
2013-01-24 15:42     ` Joe MacDonald [this message]

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=20130124154223.GH3496@windriver.com \
    --to=joe.macdonald@windriver.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox