This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc 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]

[Bug dynamic-link/21847] New: ppc64le: expected localentry:0 `pthread_…' ld.so error prevents allocation startup


https://sourceware.org/bugzilla/show_bug.cgi?id=21847

            Bug ID: 21847
           Summary: ppc64le: expected localentry:0 `pthread_…' ld.so error
                    prevents allocation startup
           Product: glibc
           Version: 2.26
            Status: NEW
          Severity: normal
          Priority: P2
         Component: dynamic-link
          Assignee: unassigned at sourceware dot org
          Reporter: fweimer at redhat dot com
                CC: jistone at redhat dot com
  Target Milestone: ---

I don't know if this is a glibc bug or not.  On ppc64le with recent binutils
2.29, applicaitons fail to start with errors like:

./bin/rustc: error while loading shared libraries:
./lib/libstd-c3a1748e15265da7.so: expected localentry:0
`pthread_condattr_destroy'
/usr/bin/cmake: error while loading shared libraries: /lib64/libcurl.so.4:
expected localentry:0 `pthread_mutex_destroy'
./dsimpletest: error while loading shared libraries:
../lib/libmumps_common-5.1.1.so: expected localentry:0 `pthread_cond_init'

The common theme seems to be that this only affects symbols which live both in
libpthread and libc.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

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