On 3 February 2017 at 00:17, Burton, Ross <ross.bur...@intel.com> wrote: > > On 30 January 2017 at 07:47, Nathan Rossi <nat...@nathanrossi.com> wrote: >> >> Due to pkg-config support for libgcrypt being un-available for upstream >> libgcrypt, some packages that depend on libgcrypt rely on the use of >> libgcrypt-config (e.g. QEMU). > > > We disable those scripts for a good reason: they're generally either broken > entirely in a cross-environment, or fail badly if sstate is used. A > better solution really is to just patch qemu's configure (yes, I know this > sucks). >
Agreed, at first that was the approach I went for, even went so far as to sending a patch upstream for QEMU (before realizing that libgcrypt upstream doesn't have pkgconfig). But upstream QEMU are not to interested in having such change. https://patchwork.ozlabs.org/patch/711018/ However since this is not really required for the QEMU in oe-core, this patch can be dropped from the series and I will sort this out by patching the configure in the QEMU recipe that needs this. Should I send a v2 of this series which removes this patch? Regards, Nathan -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
