Messages in this thread | | | Subject | Re: [PATCH v2] um: Avoid longjmp/setjmp symbol clashes with libpthread.a | From | Richard Weinberger <> | Date | Thu, 1 Jun 2017 22:58:46 +0200 |
| |
Florian,
Am 01.06.2017 um 22:53 schrieb Florian Fainelli: >> This is exactly why we have this mess right now. Everybody is just focusing >> on his own stuff. > > No, we have this mess right now because you applied patches before and > now you realize that this broke other people's system based on their > attempts to fix it. Don't blame it on people trying to fix things, this > is the worse possible attitude.
Let's calm down a bit. All I want is that we understand all issues before applying partial fixes.
>>> I don't know what the issue Thomas is having (he is now CC'd) and I >>> still don't understand why you insist on conflating the symbol clash >>> while statically linking with support for newer x86 FPU stuff... >> >> The said commits introduced issues, you face some, Thomas is facing some. >> I want them to get fixed or at least understood before we apply new patches. > > Well, I would very much like to know what Thomas' issues are, a link to > his findings would be helpful to begin with instead of just waving that > flag.
Sorry, I thought you are CC'ed. Thomas please speak up. AFAIR UML fails to boot on one of your new Laptops.
Thanks, //richard
| |