From: "Peter A. Bigot" <pab@pabigot.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] cups: extend cups-no-gcrypt.patch to apply to configure script
Date: Mon, 14 Jul 2014 10:33:06 -0500 [thread overview]
Message-ID: <53C3F832.8010307@pabigot.com> (raw)
In-Reply-To: <CAJTo0LbzhpJb_CMkqRy6etVJnah0HACkP8k_8mKw3A+8s5kkwg@mail.gmail.com>
On 07/14/2014 09:37 AM, Burton, Ross wrote:
> On 12 July 2014 03:42, Peter A. Bigot <pab@pabigot.com> wrote:
>> The original patch removed gcrypt from an m4 source file that
>> contributes to configure.in, but didn't apply those changes to or
>> rebuild the configure script itself. This allowed libgcrypt-config to
>> be found, adding native libraries to the target build.
> I'm really not happy with maintaining patches to generated files, do
> you know why we don't use the usual autotools class to re-generate the
> configure script at build time?
No; it was that way when I found it, and I'm still too rusty on yocto to
do it the right way. If you can point me to a recipe that does this
I'll try to rework it (and resubmit based on openembedded-core instead
of poky).
(FWIW: The issue doesn't show up building cups; it shows up with
core-image-lsb building ghostscript which believes cups-config's lie
that it needs -L/lib/x86_64-linux-gnu to find the gcrypt libraries that
it doesn't reference.)
Peter
prev parent reply other threads:[~2014-07-14 15:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-12 2:42 [meta-oe][PATCH] cups: extend cups-no-gcrypt.patch to apply to configure script Peter A. Bigot
2014-07-14 14:37 ` Burton, Ross
2014-07-14 15:33 ` Peter A. Bigot [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=53C3F832.8010307@pabigot.com \
--to=pab@pabigot.com \
--cc=openembedded-core@lists.openembedded.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.