From: Florian Fainelli <f.fainelli@gmail.com>
To: Richard Weinberger <richard@nod.at>,
linux-kernel@vger.kernel.org, Thomas Meyer <thomas@m3y3r.de>
Cc: Jeff Dike <jdike@addtoit.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>,
"open list:USER-MODE LINUX (UML)"
<user-mode-linux-devel@lists.sourceforge.net>,
"open list:USER-MODE LINUX (UML)"
<user-mode-linux-user@lists.sourceforge.net>
Subject: Re: [PATCH v2] um: Avoid longjmp/setjmp symbol clashes with libpthread.a
Date: Thu, 1 Jun 2017 13:40:01 -0700 [thread overview]
Message-ID: <f57b5906-30cc-0fdf-893c-39e4f5202d1b@gmail.com> (raw)
In-Reply-To: <85f8b8c0-cf0e-3c67-c237-be4b045c617b@nod.at>
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
next prev parent reply other threads:[~2017-06-01 20:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 0:32 [PATCH v2] um: Avoid longjmp/setjmp symbol clashes with libpthread.a Florian Fainelli
2017-05-24 0:32 ` Florian Fainelli
2017-05-24 7:02 ` Richard Weinberger
2017-05-24 16:19 ` Florian Fainelli
2017-06-01 19:38 ` Florian Fainelli
2017-06-01 20:11 ` [uml-devel] " Richard Weinberger
2017-06-01 20:11 ` Richard Weinberger
2017-06-01 20:15 ` Florian Fainelli
2017-06-01 20:17 ` [uml-devel] " Richard Weinberger
2017-06-01 20:17 ` Richard Weinberger
2017-06-01 20:40 ` Florian Fainelli [this message]
2017-06-01 20:44 ` Richard Weinberger
2017-06-01 20:53 ` Florian Fainelli
2017-06-01 20:58 ` Richard Weinberger
2017-06-01 21:25 ` Thomas Meyer
2017-06-02 5:49 ` Florian Fainelli
2017-06-02 7:38 ` Richard Weinberger
2017-06-03 21:25 ` Thomas Meyer
2017-06-03 21:36 ` Richard Weinberger
2017-06-02 8:04 ` Thomas Meyer
2017-06-02 8:30 ` Richard Weinberger
2017-06-02 9:15 ` Thomas Meyer
2017-06-02 13:18 ` Thomas Meyer
2017-06-05 19:32 ` Florian Fainelli
2017-06-05 19:34 ` Richard Weinberger
2017-06-28 22:40 ` Florian Fainelli
2017-06-29 7:25 ` [uml-devel] " Richard Weinberger
2017-06-29 7:25 ` Richard Weinberger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f57b5906-30cc-0fdf-893c-39e4f5202d1b@gmail.com \
--to=f.fainelli@gmail.com \
--cc=hpa@zytor.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=richard@nod.at \
--cc=tglx@linutronix.de \
--cc=thomas@m3y3r.de \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.