On Tue, Jul 27, 2021 at 12:24 AM Richard Purdie <richard.pur...@linuxfoundation.org> wrote: > > On Mon, 2021-07-26 at 14:40 -1000, Steve Sakoman wrote: > > On Mon, Jul 26, 2021 at 12:27 PM Ruslan Babayev (fib) <f...@cisco.com> > > wrote: > > > > > > Hi Steve, > > > > > > Thanks for reviewing the patches. I understand the problem of merging this > > > patch as is. > > > But Dunfell currently has a host contamination issue on systems with zstd > > > installed as part of base OS resulting in broken cmake-native recipe. Can > > > you help bring this up to the attention of the steering committee? > > > > Perhaps Richard can comment on this. You are asking for a feature > > change to dunfell that involves modifications in both > > openembedded-core and meta-openembedded. So both technical steering > > committees would need to agree that this is appropriate. > > We don't have to go straight to the TSC, the layer maintainers can try and > agree a plan first. > > I've added Armin as meta-openembedded maintainer for dunfell. > > Context: cmake-native suffers host contamination on dunfell due to zstd being > detected on the host. The upstream cmake community say they don't support > configuring it without it. > > Do we agree we should move zstd from meta-oe to oe-core in dunfell to fix > this? Should we patch cmake in dunfell to try and use it's own copy of zstd > internally? The latter is more risky in that we've not tried that and multiple > configures can be 'fun' in builds. Moving the recipe has a different kind of > pain.
There's no need to move the recipe, just adding to oe-core should be enough.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#154177): https://lists.openembedded.org/g/openembedded-core/message/154177 Mute This Topic: https://lists.openembedded.org/mt/84410822/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
