"symbol __pthread_initialize, version GLIBC_2.0 not defined in file libpthread.so.0"
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
the only other thing i can think of and this is a way long shot because of compiler differences
try to to compile a version of glibc2.0
remember of course to put it somepace safe /opt/glibc2.0 or something in the unlikely event it will compile
remember to get the glibc-linuxthreads packages that went with it and unpack them inside the
glibc directory might want the glibc-crypt that went with it as well to be on the safe side
some of those old glibc and you passed some parameters with a configparms file so do
./configure --help and use prefix slibdir sysconfdir in the configure if you can or
configure --with-gnu-binutils --enable-shared --enable-add-ons=linuxthreads,crypt
make a file configparms with you safe values
# Begin configparms
# End configparms
then try LD_CONFIG_PATH to load it for your program
have no idea if this will work either
that is a very old gibc