All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Crowe <mac@mcrowe.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libgcrypt: Revert to inheriting from binconfig
Date: Thu, 25 May 2017 17:37:45 +0100	[thread overview]
Message-ID: <20170525163745.GA16458@mcrowe.com> (raw)
In-Reply-To: <1495665889.25229.32.camel@linuxfoundation.org>

On Wednesday 24 May 2017 at 23:44:49 +0100, Richard Purdie wrote:
> On Wed, 2017-05-24 at 17:25 +0100, Burton, Ross wrote:
> > 
> > On 24 May 2017 at 14:52, Mike Crowe <mac@mcrowe.com> wrote:
> > > Oh, I thought that binconfig.bbclass swung through hoops in order
> > > to make
> > > the scripts work well enough. Is that not true?
> > > 
> > > Many other recipes are still inheriting binconfig rather than
> > > binconfig-disabled: apr, curl, gnutls, libtasn1.
> > > 
> > binconfig goes through hoops that are just not required with
> > pkgconfig, and the hoops are hacks which may not be reliable.  I
> > can't remember the details but I do remember that libgcrypt/gnupg was
> > a worst offender here.
> > 
> > CCing Richard to see if he can remember why.
> > 
> > In the glorious future removing all binconfig scripts would be the
> > ideal, in my opinion.  Alternatively replacing them with glorified
> > pkgconfig wrappers.
> 
> We made a choice back then to go ahead and migrate these pieces to pkg-
> config regardless of upstream's views since its so much cleaner and
> less error prone than -config shell scripts which need hacking. We do
> also patch the autoconf macros those pieces of software ship so that
> pkg-config is used by the standard macros which covers most users
> (since we reautoconf software).

[snip]

> I appreciate that does cause some pain as we're doing something
> differently but I also believe it is justified. I would suggest
> reminding these upstreams who won't at least allow pkg-config in
> parallel that this does cause pain in the hope that if multiple people
> report it, they may rethink things.

I was unaware that oe-core's libgcrypt recipe provides a modified
libgcrypt.m4 in share/aclocal/ that uses pkg-config.

Inspired by the oe-core gnupg recipe, I deleted m4/libgcrypt.m4 from the
libmicrohttpd source directory in a do_configure_prepend and everything now
seems happy.

Thanks, and sorry for the unnecessary diversion.

Mike.


      reply	other threads:[~2017-05-25 16:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-24 13:23 [PATCH] libgcrypt: Revert to inheriting from binconfig Mike Crowe
2017-05-24 13:28 ` Burton, Ross
2017-05-24 13:52   ` Mike Crowe
2017-05-24 16:25     ` Burton, Ross
2017-05-24 22:44       ` Richard Purdie
2017-05-25 16:37         ` Mike Crowe [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=20170525163745.GA16458@mcrowe.com \
    --to=mac@mcrowe.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=ross.burton@intel.com \
    /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.