Home > Relocation Error > Relocation Error /lib/tls/libpthread.so.0

Relocation Error /lib/tls/libpthread.so.0

Why didn't it like /lib/tls/libpthread.so.0 ? As a general-purpose set of compilers, GCC produces...https://books.google.com.tr/books/about/The_Definitive_Guide_to_GCC.html?hl=tr&id=wQ6r3UTivJgC&utm_source=gb-gplus-shareThe Definitive Guide to GCCKütüphanemYardımGelişmiş Kitap AramaE-Kitap satın al - 86,63 ₺Bu kitabı basılı olarak edininApress.comAmazon.co.ukidefixKütüphanede bulTüm satıcılar»The Definitive Guide to GCCWilliam von HagenApress, 29 I'd say that the documentation on hwcap in ldconfig needs improvement. -- Back to top Nix*nix forums Guru WannabeJoined: 28 Feb 2005 Posts: 118 Posted: Wed Dec 07, 2005 4:04 pm GCC has long been available for most major hardware and operating system platforms and is often the preferred family of compilers. http://supercgis.com/relocation-error/relocation-error-lib-libpthread-so-0.html

However, I can't get a simple example Qt program running on the new OS. You can't mix and match different versions of libc and libpthread. Thanks! Back to top mkcolgJoined: 30 Jun 2004Posts: 6773Location: The Portland Group Inc. https://bugzilla.redhat.com/show_bug.cgi?id=113000

Results 1 to 7 of 7 LinkBack LinkBack URL About LinkBacks Bookmark & Share Add Thread to del.icio.usTweet this thread Thread Tools Show Printable Version Email this Page… Subscribe to this Try LD_LIBRARY_PATH=/usr/lib/debug instead. -- Daniel Jacobowitz CodeSourcery References: Relocation error in gdb From: Williams, Allen Index Nav: [DateIndex] [SubjectIndex] [AuthorIndex] [ThreadIndex] Message Nav: [DatePrev][DateNext] [ThreadPrev][ThreadNext] HesabımAramaHaritalarYouTubePlayHaberlerGmailDriveTakvimGoogle+ÇeviriFotoğraflarDaha fazlasıDokümanlarBloggerKişilerHangoutsGoogle'a ait daha da fazla Home Questions Office Help Forum New Posts FAQ Calendar Forum Actions Mark Forums Read Quick Links Today's Posts Ask a Question Excel Microsoft Word PowerPoint Advanced Search Forum Operating Systems Linux The output above means that loader will not use it on kernels older than 2.4.20 If your target kernel is "new enough", also check LD_ASSUME_KERNEL environment variable.

Bruno Reply With Quote 02-21, 08:37 PM #6 Re: What relation between "libc.so.6" and symbol version "GLIBC_2.x" ? The entries /lib/tls/{i486,i586} above support this view. reply | permalink Pierre Bourgin Bisbal, Prentice wrote: [...] So you should modify $LD_LIBRARY_PATH to use the older libpthread.so, the one from the compat-glibc package. or is it with my embedded 2.6.18 filesystem?

This was most helpful. using its updater/installer) is on the 'real' system. I'm hoping someone here on this list canshed more light on the cause and solution.PowerPath appears to be working just fine./opt/Navisphere/bin/naviagent: relocation error:/opt/Navisphere/bin/naviagent:symbol __pthread_atfork, version GLIBC_2.0 not defined in filelibpthread.so.0 with i486 requires 'movw' to access the segment registers, while i686 can use 'movl' [shorter because no prefix byte] as long as you're content with 16 high bits of garbage.

The exact error is: ourexecutable: relocation error: ourexecutable: symbol __pthread_initialize, version GLIBC_PRIVATE not defined in file libpthread.so.0 with link time reference An ldd on ourexecutable produces: linux-gate.so.1 => (0x00ed1000) librt.so.1 => the same toolchain and identical libraries (verified using md5sum). To fix, remove "libpthread.so" from the PGI lib directory and recreate the "libpgthread.so" symlink. John Reiser <[email protected]> writes: Quote: The difference between /lib/libpthread.so and /lib/tls/libpthread.so.0 has to do with i486 vs.

Quote: Any suggestions/tips are much appreciated, as I'm basically stuck right now. their explanation This I think is the key to the problem, but I don't really know where to go with it. - I have a 'hello world' program that runs fine on the Basically there are two shared libraries required for pthreads, not just /lib/tls/libpthread.so.0 as reported by 'ldd'. You mean /lib/tls/libpthread.so.0 However it doesn't seem to mmap() anything as it does on the development box.

So there's no point. (Or, more likely, he'd just ignore it completely, as has happened with all docs I've tried to contribute to glibc to date. weblink It is the key. As a general-purpose set of compilers, GCC produces high-quality, fast code. When I try to start naviagent, I get the errorbelow.

The app runs fine on my development box, but on the target it gives the error: "error while loading shared libraries: libpthread.so.0: cannot open shared object file: No such file or Hope this helps you out. I took your advice and read theld.so man page. navigate here Again, it makes no difference in PGI's behavior.

Thanks! Why ldd returns different results ? I've copied all necessary libraries (/lib/tls/libpthread.so.0, etc) onto the target board.

What I'd like to see is the output of the following commands: Code: ls -l /lib64/libpthread.so.0 ls -l /lib64/tls/libpthread.so.0 pgcc test.c -v -lpthread -o test.pgi echo $LD_LIBRARY_PATH ldd test.pgi test.pgi Also,

Any suggestions/tips are much appreciated, as I'm basically stuck right now. kmail 3. I solved the problem by using the static libraries in /usr/lib/. Copyright (C) 2005 Free Software Foundation, Inc.

The output above means that loader will not use it on kernels older than 2.4.20 If your target kernel is "new enough", also check LD_ASSUME_KERNEL environment variable. It would appear that this is the case, *except* for libpthread which is causing these problems. Thanks, Mat Back to top troytJoined: 26 Apr 2005Posts: 4 Posted: Fri Apr 29, 2005 10:30 am Post subject: Sry reply took so long... http://supercgis.com/relocation-error/relocation-error.html Comment 4 Need Real Name 2004-01-07 16:36:39 EST Yepp, helped.

William has written articles and software reviews for publications including Linux Magazine, Linux Format (UK), Maximum Linux, Mac Tech Magazine, Mac Home Magazine, and Mac Directory, and he has written extensive Follow-Ups: Re: dynamic linker problem with libpthread.so.0? I'm using a 'hello thread' program to test with, that basically creates a thread that prints something, then joins and exits. - the kernel versions are the same on both the I've removed entries from ld.so.conf that relate to other non-gcc non-pgi compilers, just in case there may be some sort of conflict.

I've tried about everything I can think of. That smells like you have a wrong libc.so.6 somewhere in the library search path. I've actually ran the test.c compile from the 'real' system just to ensure that everything listed above are identical to the results from within the 'chroot' -- they are. Quote: there should not be a "libpthread.so" in the PGI lib directory.

John Reiser probably can help us here. On i386, this does indeed correspond to .x86_capability[]. And libpgthread pointed to /lib64/libpthread.so.0. When I try to start naviagent, I get the errorbelow.

Thanks, Mark Back to top Paul Pluzhnikov*nix forums GuruJoined: 25 Mar 2005 Posts: 512 Posted: Tue Dec 06, 2005 9:04 am Post subject: Re: dynamic linker problem with libpthread.so.0? Also note that you don't need /lib/{i686,tls}/* on the target at all (if your target is an i486, which is apparently the case). It wasn't nearly as complicated as I thought. And the same kernel?

Back to top mkcolgJoined: 30 Jun 2004Posts: 6773Location: The Portland Group Inc. It would appear that this is the case, *except* for libpthread which is causing these problems. Here is some more info based on your reply, I'd be interested to hear what you think. From glibc's POV, they come from the glibc source tree in dl-procinfo.h, e.g.

Quote: the same toolchain and identical libraries (verified using md5sum). And the same kernel?