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.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am trying to run Celtx on SuSE 10.0 which requires glibc-2.4+ (current version is 2.3.5-40). The error message I am getting from celtx is /lib/tls/libc.so.6: version `GLIBC_2.4' not found (required by /usr/local/celtx/celtx-bin). I've tried building glibc-2.4, 2.5.1, 2.6, 2.8, and 2.10.1 using gcc-4.0.2 with mixed error messages. The most promising are 2.4 and 2.8, since I'm getting past the 'configure' and 'make' phases with only minor 'make check' errors. I was not able to build gcc-4.3.4 which would allow me to build the latest glibc-2.10.1, I think because I am missing mpfr headers even though I built mpfr-2.4.1 library successfully. Unfortunately the easy way out by upgrading to a new flavor *nix is not an option, as SuSE 10 exists on one monolithic partition together with /home directory, and Open SuSE would require new install, not an upgrade. I have glibc-2.8 built in /usr/local/lib/glibc_testing/ but I am not able to "coax" celtx to launch using
When I query gcc --print-file-name=libc.so.6 I get /lib/libc.so.6 (old version) although I have libc.so.6 @-> libc-2.8.so in the built directory. Celtx responds with "invalid ELF headers" message. If I could get celtx to run, I would go ahead with the new library. Is there any other way to test it?
For example, the following works
Code:
/usr/local/lib/glibc_testing/lib/ld-linux.so.2 --library-path /usr/local/lib/glibc_testing/lib:/lib /usr/bin/find --version
GNU find version 4.2.23
Features enabled: D_TYPE O_NOFOLLOW(enabled)
Regards,
Jack
Last edited by bufo; 09-04-2009 at 04:36 AM.
Reason: clarification
Thanks for the tip, however, I am getting "segmentation fault" using the LD_LIBRARY_PATH constant. A new can of worms. Could not launch gdb or any other program unfortunately.
Distribution: PCLinuxOS2023 Fedora38 + 50+ other Linux OS, for test only.
Posts: 17,511
Rep:
Well, first : you can't have Suse 10.0 forever ( probably.)
Celtx or no Celtx, you will need a plan how to backup /
reinstall your /home etc. : theoretically the hard disk
can stop working to-morrow.
After having a full backup on both an extra hard disk
and some DVD rom's /home can be re-established
anywhere.
Or set up Suse 10.3 ( glibc 2.6 ) on a spare hard disk
or partition.
You are absolutely correct! I'm running no fewer than five different flavors of Linux. I must be "crackers," can't get enough of this stuff. The problem that I wanted to solve was an 'incremental' upgrade, so you'd think 2.3.5-40 is only a few millimeters from 2.40. Yeah, let me introduce you to the folks, they have a bridge for sale! With gcc-4.0.2 it should be *possible* to walk on water. I've built all the major glibc versions (almost). The dep libs you can build without a hitch, but not so for the major sys library, the list of requirements is a mile long. It could be done, in 3 weeks! The build begins with a fresh, clean slate and you builds components from sources, not upgrading 5-6 year old dog to do new tricks. I'm sorry to say, I've disestablished myself from Software und Systems Entwickelung. Guess which flavors I have considered. (You have only three guesses!) Hint this is a single core Centrino 1.60 with 512 RAM and 60 GB disk.
Out of curiosity I've tried building glibc-2.10.1 on the new system, and it also failed. There is no mystery here, the body of the function syslog.c cannot find function vsyslog_chk. Good luck tracking that one. The problem here is negligence. There ought to be 2 versions of the library, one fully documented with all the *mysterious* dependencies, and the release version from which the documentation has been either stripped or extracted into a supporting doc file. That would be asking too much, since programmers don't have all 10 fingers in general.
/tmp/glibc-2.10.1/build_glibc_2101/misc/syslog.o.dt -MT /home/bufo/tmp/glibc-2.10.1/build_glibc_2101/misc/syslog.o
../misc/syslog.c: In function ‘__vsyslog_chk’:
../misc/syslog.c:123: sorry, unimplemented: inlining failed in call to ‘syslog’: function body not available
../misc/syslog.c:155: sorry, unimplemented: called from here
make[2]: *** [/home/bufo/tmp/glibc-2.10.1/build_glibc_2101/misc/syslog.o] Error 1
make[2]: Leaving directory `/home/bufo/tmp/glibc-2.10.1/misc'
make[1]: *** [misc/subdir_lib] Error 2
make[1]: Leaving directory `/home/bufo/tmp/glibc-2.10.1'
make: *** [all] Error 2
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.