From: Richard Weinberger <richard@nod.at>
To: Keno Fischer <keno@juliacomputing.com>
Cc: linux-kernel@vger.kernel.org, jdike@addtoit.com,
user-mode-linux-devel@lists.sourceforge.net,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [PATCH] um: Fix compile failure due to current_text_address() definition
Date: Thu, 10 Nov 2016 21:19:16 +0100 [thread overview]
Message-ID: <eaa15fe0-dee2-3969-012a-9a0356acc069@nod.at> (raw)
In-Reply-To: <CABV8kRyr+PZmfd8B+rN2vWfbnmjmp85oGH_BU7zbUyqDQt+NxQ@mail.gmail.com>
Keno,
On 10.11.2016 21:14, Keno Fischer wrote:
> Yes
Can you please reply to Sebastian's patch series and explain him how you trigger
that error?
I don't have a gcc broken by Debian on my machine right now.
> On Thu, Nov 10, 2016 at 3:14 PM, Richard Weinberger <richard@nod.at> wrote:
>> Keno,
>>
>> On 10.11.2016 21:10, Keno Fischer wrote:
>>>> The problem is ready being solved in a generic way:
>>>> http://marc.info/?l=linux-kernel&m=147828481602561&w=2
>>>>
>>>> Can you please give this patch a try?
>>>
>>> No dice. After backing out my patch and applying that one I get:
>>>
>>> /usr/bin/ld: error: net/built-in.o: requires unsupported dynamic reloc
>>> 11; recompile with -fPIC
>>
>> But you applied the whole series, right?
Thanks,
//richard
next prev parent reply other threads:[~2016-11-10 20:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 1:53 [PATCH] um: Fix compile failure due to current_text_address() definition Keno Fischer
2016-11-10 8:05 ` Richard Weinberger
2016-11-10 20:10 ` Keno Fischer
2016-11-10 20:14 ` Richard Weinberger
2016-11-10 20:14 ` Keno Fischer
2016-11-10 20:19 ` Richard Weinberger [this message]
2016-11-10 20:46 ` Keno Fischer
2016-11-11 10:34 ` Richard Weinberger
2016-11-11 21:03 ` Keno Fischer
2016-11-11 22:07 ` Richard Weinberger
2016-11-16 3:45 ` Keno Fischer
2016-11-16 14:36 ` 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=eaa15fe0-dee2-3969-012a-9a0356acc069@nod.at \
--to=richard@nod.at \
--cc=bigeasy@linutronix.de \
--cc=jdike@addtoit.com \
--cc=keno@juliacomputing.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).