Messages in this thread | | | Subject | Re: [PATCH v2] um: Avoid longjmp/setjmp symbol clashes with libpthread.a | From | Florian Fainelli <> | Date | Thu, 1 Jun 2017 13:40:01 -0700 |
| |
On 06/01/2017 01:17 PM, Richard Weinberger wrote: > Am 01.06.2017 um 22:15 schrieb Florian Fainelli: >> On 06/01/2017 01:11 PM, Richard Weinberger wrote: >>> Florian, >>> >>> Am 01.06.2017 um 21:38 schrieb Florian Fainelli: >>>>> Presumably because we are not using the same glibc version? The one I >>>>> have installed on this machine is glibc-2.12, do you want me to attach a >>>>> copy of it? >>>> >>>> Richard, what do we do with this? >>> >>> I'd like to see the issues that Thomas sees also get addressed. >> >> Sure, but that seems orthogonal? In the absence of an answer from Eli, >> either you could take my patch or just send reverts of Eli's two >> commits, whichever you prefer. > > Or you and Thomas could investigate. :-)
Honestly, I don't know what do you want me to investigate, my host machine is old (2.6.32) and does not support PTRACE_GETREGSET or friends, nor does it have _xstate, so with that, we either don't use those period, which would be a revert, or we just conditionally build support for that (my patch) and everyone is happy.
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... -- Florian
| |