I trust the upstream will figure this out. My goal is to avoid adding more patches that are declared unsuitable for upstream, and so have to be rebased until the end of time by (usually) me.
Alex On Wed, 24 Aug 2022 at 10:28, Andrei Gherzan <[email protected]> wrote: > > On Wed, 24 Aug 2022, at 09:21, Alexander Kanavin wrote: > > The issue is described by you in the commit message? I think this is > > good enough for upstream submission as is, as long as you edit out the > > yocto specific references. > > RIght. I was more interested in how you see this issue per se. At the end of > the day, it is not a bug, it is more of a warning/log message while the > functionality is in place. What would you expect upstream to do? > > Of course, there are a couple of options here. Compile macro for musl, change > the log format for that specific message, etc. But it can also be treated as > a dynamic check with an associated log message. > > Andrei
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#169788): https://lists.openembedded.org/g/openembedded-core/message/169788 Mute This Topic: https://lists.openembedded.org/mt/93217143/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
