This is the mail archive of the mailing list for the binutils project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: ppc64le: expected localentry:0 `pthread_condattr_destroy'

On 07/26/2017 06:34 PM, Josh Stone wrote:
> On 07/26/2017 12:13 PM, Carlos O'Donell wrote:
>> On 07/25/2017 09:11 PM, Josh Stone wrote:
>>> Hi folks,
>>> I mentioned this regression to fweimer, and he suggested I should bring
>>> it up to libc-alpha and binutils.  I was just trying to rebuild rustc on
>>> Fedora Rawhide, and ppc64le alone failed with this localentry error.
>>> Florian suspected that a binutils update in particular now enabled use
>>> I reproduced the regression from old to new binutils, and uploaded those
>>> artifacts here if anyone else wants to inspect them:
>>> rust-1.19.0-stage1-ppc64le-binutils-2.28:
>>> # LD_LIBRARY_PATH=./lib ./bin/rustc -V
>>> rustc 1.19.0
>>> rust-1.19.0-stage1-ppc64le-binutils-2.29:
>>> # LD_LIBRARY_PATH=./lib ./bin/rustc -V
>>> ./bin/rustc: error while loading shared libraries:
>>> ./lib/ expected localentry:0
>>> `pthread_condattr_destroy'
>> Right, this looks like a ppc64le-specific (ELFv2) regression in the unreleased
>> binutils 2.29. I've not seen this with the release 2.28.
> It does appear to be released -- binutils-2_29 was tagged on Monday.
> But anyway, are you seeing this in other contexts yourself?
No, you are the first person I've seen run into this issue.

I suggest you file a binutils bug right away to get this fixed,
or find out what is going wrong with the rust linkage of that
shared object. It could be something wrong with your invocation
of `ld' if you're doing that manually. When invoking ld without
using gcc as the driver you must be acutely aware of all the
required options to produce a functioning link.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]