From: Steve Grubb <sgrubb@redhat.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Drop Posix Capabilities
Date: Sat, 26 Sep 2009 10:29:06 -0400 [thread overview]
Message-ID: <200909261029.06609.sgrubb@redhat.com> (raw)
In-Reply-To: <1253914521.2659.1.camel@localhost.localdomain>
On Friday 25 September 2009 05:35:21 pm Marcel Holtmann wrote:
> > diff -urp bluez-4.54.orig/acinclude.m4 bluez-4.54/acinclude.m4
> > --- bluez-4.54.orig/acinclude.m4 2009-09-25 11:33:47.000000000 -0400
> > +++ bluez-4.54/acinclude.m4 2009-09-25 16:38:32.000000000 -0400
> > @@ -352,3 +352,36 @@ AC_DEFUN([AC_ARG_BLUEZ], [
> > AM_CONDITIONAL(CONFIGFILES, test "${configfiles_enable}" = "yes")
> > AM_CONDITIONAL(CABLE, test "${cable_enable}" = "yes" && test
> > "${cable_found}" = "yes") ])
>
> please base the patch against upstream and not the Fedora package.
I just retried against the 4.54 tarball and it applies, but with some fuzz.
patch -p1 < ../bluez-4.54-capability.patch
patching file acinclude.m4
Hunk #1 succeeded at 336 with fuzz 2 (offset -16 lines).
patching file configure.ac
Hunk #1 succeeded at 44 (offset -1 lines).
patching file Makefile.am
Hunk #1 succeeded at 191 (offset -9 lines).
patching file src/main.c
> > +AC_DEFUN([LIBCAP_NG_PATH],
> > +[
> > + AC_ARG_WITH(libcap-ng,
> > + [ --with-libcap-ng=[auto/yes/no] Add Libcap-ng support
> > + [default=auto]],, with_libcap_ng=auto)
> > +
>
> I mention this to Bastien already. I want pkgconfig support here and not
> some old style aclocal magic.
libcap-ng itself does not provide any pkgconfig support. I'll check on this.
-Steve
next prev parent reply other threads:[~2009-09-26 14:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 20:47 [PATCH] Drop Posix Capabilities Steve Grubb
2009-09-25 21:35 ` Marcel Holtmann
2009-09-26 14:29 ` Steve Grubb [this message]
2009-09-27 20:31 ` Marcel Holtmann
2009-09-28 21:31 ` Steve Grubb
2009-09-28 23:40 ` Marcel Holtmann
2009-09-29 13:00 ` Steve Grubb
2009-09-29 18:03 ` Marcel Holtmann
2009-10-02 9:46 ` Marcel Holtmann
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=200909261029.06609.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=linux-bluetooth@vger.kernel.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.