Re: [OE-core] [meta-oe][PATCH v3] libepoxy: New recipe updated to latest release

ists.openembedded.org] On Behalf Of >>> > Francesco Giancane >>> > Sent: den 28 februari 2018 23:09 >>> > To: openembedded-core@lists.openembedded.org >>> > Subject: [OE-core] [meta-oe][PATCH v3] libepoxy: New recipe updated to >>> latest releas

Re: [OE-core] [meta-oe][PATCH v3] libepoxy: New recipe updated to latest release

ists.openembedded.org >> > [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of >> > Francesco Giancane >> > Sent: den 28 februari 2018 23:09 >> > To: openembedded-core@lists.openembedded.org >> > Subject: [OE-core] [meta-oe][PATCH v3] libepoxy:

Re: [OE-core] [meta-oe][PATCH v3] libepoxy: New recipe updated to latest release

s.openembedded.org > > [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of > > Francesco Giancane > > Sent: den 28 februari 2018 23:09 > > To: openembedded-core@lists.openembedded.org > > Subject: [OE-core] [meta-oe][PATCH v3] libepoxy: New recipe updated to > lat

Re: [OE-core] [meta-oe][PATCH v3] libepoxy: New recipe updated to latest release

core] [meta-oe][PATCH v3] libepoxy: New recipe updated to latest > release This isn't in meta-oe, it's in meta. ;) I suggest changing the subject to: libepoxy: Update to 1.5.0 since it's not a new recipe, and "latest release" carries a lot less information than the actual version.

Re: [OE-core] [meta-oe][PATCH v3] libepoxy: New recipe updated to latest release

Hi, Sorry again. The patch was based on openembedded-core rather than poky, and this is why the patchwork failed to apply it. This should be the last one. Thanks for the patience, Francesco Giancane 2018-02-28 23:08 GMT+01:00 Francesco Giancane : > libepoxy

[OE-core] [meta-oe][PATCH v3] libepoxy: New recipe updated to latest release

libepoxy 1.4.3 did not compile successfully because of implicit symbol definitions and link-time errors. A new recipe with latest libepoxy release (1.5.0) which successfully compiles is provided. Patch to disable 'dlvsym' has also been forward-ported to be applicable to version 1.5.0. The patch