From: Florian Weimer <fweimer@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Markus Trippelsdorf <markus@trippelsdorf.de>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: commit cfafcd117 "futex: Rework futex_lock_pi() to use rt_mutex_*_proxy_lock()" causes glibc nptl/tst-robustpi8 failure
Date: Thu, 18 May 2017 10:42:58 +0200 [thread overview]
Message-ID: <1c5fdfa0-11cd-1819-9696-6d837195c5b6@redhat.com> (raw)
In-Reply-To: <20170518084141.nbijbcli6nasymzs@hirez.programming.kicks-ass.net>
On 05/18/2017 10:41 AM, Peter Zijlstra wrote:
> On Thu, May 18, 2017 at 10:34:34AM +0200, Florian Weimer wrote:
>> On 05/18/2017 10:31 AM, Peter Zijlstra wrote:
>>> That more or less worked, it still failed:
>>>
>>> /usr/bin/ld: /usr/local/src/glibc/build/nptl/tst-once5.o: relocation R_X86_64_32 against `.text' can not be used when making a shared object; recompile with -fPIC
>>> /usr/bin/ld: final link failed: Nonrepresentable section on output
>>> collect2: error: ld returned 1 exit status
>>
>> I think this is a bug in the binutils version shipping with Debian jessie.
>
> I am indeed on debian/testing (which is jessie just now I think), I'll
> apt-get upgrade to see if its fixed, otherwise, I'll just have to live
> with it for now.
Careful. It's fixed in *current* debian/testing (stretch), so a very
large upgrade might be waiting for you.
Florian
next prev parent reply other threads:[~2017-05-18 8:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 17:36 Markus Trippelsdorf
2017-05-17 17:50 ` Florian Weimer
2017-05-18 6:46 ` Peter Zijlstra
2017-05-18 6:57 ` Peter Zijlstra
2017-05-18 7:40 ` Peter Zijlstra
2017-05-18 8:04 ` Markus Trippelsdorf
2017-05-18 8:14 ` Peter Zijlstra
2017-05-18 8:12 ` Florian Weimer
2017-05-18 8:31 ` Peter Zijlstra
2017-05-18 8:34 ` Florian Weimer
2017-05-18 8:41 ` Peter Zijlstra
2017-05-18 8:42 ` Florian Weimer [this message]
2017-05-18 11:43 ` Peter Zijlstra
2017-05-18 12:30 ` Peter Zijlstra
2017-05-19 15:48 ` Peter Zijlstra
2017-05-19 16:07 ` Peter Zijlstra
2017-05-19 17:35 ` Markus Trippelsdorf
2017-05-22 20:04 ` [tip:locking/urgent] futex,rt_mutex: Fix rt_mutex_cleanup_proxy_lock() tip-bot for Peter Zijlstra
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=1c5fdfa0-11cd-1819-9696-6d837195c5b6@redhat.com \
--to=fweimer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--subject='Re: commit cfafcd117 "futex: Rework futex_lock_pi() to use rt_mutex_*_proxy_lock()" causes glibc nptl/tst-robustpi8 failure' \
/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
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.