I can't do (a) at the moment since I do not have CentOS set up here. As
for (b), I think that if disabling libunwind in the libsdl2-native build
only, the impact is minimized, since libsdl2-native is used only for
other native tools like QEMU.
On 18.03.22 12:35, Richard Purdie wrote:
On Fri, 2022-03-18 at 12:08 +0100, Carlos Rafael Giani via
lists.openembedded.org wrote:
I am preparing a patch for this. I am somewhat uncertain though if this is
considered an OK approach or a hack, since we could in theory add libunwind-
native as a libsdl2-native dependency, but libunwind-native itself has build
issues, as seen here:
https://autobuilder.yoctoproject.org/typhoon/#/builders/91/builds/5624/steps/12/logs/stdio
To me, it seems that the "clean" solution would be to fix libunwind-native
then. But that may take longer (just guessing here, I have no idea about
libunwind).
Thoughts?
The key questions are:
a) Can we fix unwind-native to work on centos7 where it breaks? If so, that is
the best solution.
b) What functionality do we lose if we disable unwind in libsdl? Is it minor
debugging info or something we really do need?
I'm afraid I don't know the answers to those questions so it makes the correct
course of action hard to see.
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#163452):
https://lists.openembedded.org/g/openembedded-core/message/163452
Mute This Topic: https://lists.openembedded.org/mt/89607589/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
