LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   Updating gclib? (https://www.linuxquestions.org/questions/linux-newbie-8/updating-gclib-409432/)

Zeno McDohl 01-29-2006 05:54 PM

Updating gclib?
 
[EDIT] See below posts, I am trying to "uninstall" what I did.


I'm trying to update gclib to 2.3.6 following this tutorial, but got an error when doing the Make.
Code:

cannot set up thread-local storage: set_thread_area failed when setting up thread-local storage

make[2]: *** [/usr/src/glibc-build/sunrpc/xbootparam_prot.stmp] Error 127


320mb 01-30-2006 07:26 AM

Quote:

Note that you'll also need the latest stable version of make (at the time of this writing it is 3.80) from here:
did you upgrade the "make" package first as suggested??
Quote:

To build glibc 2.3.x, you'll also need gcc-3.x from here:
and did you upgrade the gcc package as suggested??

Zeno McDohl 01-30-2006 12:35 PM

Yes, Make is the latest stable version already.

Yes, I have gcc 3.x.

sundialsvcs 01-31-2006 10:48 AM

Glibc is special. Glibc is different. :eek: Attempting to update glibc without knowing what you are doing can render your system inoperable! :eek:

Generally, glibc is updated only as part of the process of installing a completely new distribution on the machine, or a completely new release of the same. I advise you to do likewise.

Here's why: of all of the shared libraries on your system, glibc is used by nearly all programs on your system, including ones (like init, or basic commands) without which your system cannot run or cannot be used. If you botch the update, there's no easy way to get back out.

Furthermore, glibc is dependent upon which version of the kernel you are using. If you're running a 2.4 kernel, you can't move to later versions of this library. You have to: upgrade your kernel, boot into it, build the library, bring all of the core-programs forward . . . :rolleyes:

That is to say, you have to: install a new version of your distro, following their proscribed installation procedures. Sit back and watch the blinking lights. :)

Been there... http://www.linuxfromscratch.org... done that... screwed it up once :rolleyes: ... okay, make that twice ... finally did it. Don't do it.

Zeno McDohl 02-02-2006 09:23 PM

Wait... So I followed that tutorial up to the make part (which failed)... Should I revert something? Are things changed already, and problems may arise?

foo_bar_foo 02-02-2006 10:40 PM

that tutorial is old and sucks. (person was lucky if it worked) and the stuff about the headers is odd.
don't follow instructions for the wrong version either.
basically like everyone says fix your headers back like they were and be glad you didn't get to the install part. cause then you machine most likely wouldn't work.

Zeno McDohl 02-03-2006 05:50 AM

Quote:

basically like everyone says fix your headers back like they were
No one had said that...

How do I do that?

foo_bar_foo 02-03-2006 12:54 PM

that would be to follow the instructions you cited in reverse
to reverse the instructions you followed.

Zeno McDohl 02-03-2006 02:26 PM

I still don't understand. What's the reverse of say, step #2? The reverse of doing a copy? I also don't know how to reverse the ../configure or anything.

Zeno McDohl 02-04-2006 04:43 PM

Anyone? I am a newbie here after all. Telling me to just "reverse the instructions" is a bit vague.

blz8 02-08-2007 04:17 AM

I'm getting the same error on my RH box while trying to build glibc-2.4. I've already updated gcc (4.1.1), binuntils, make, and other prereqs, so I'm good on that.

Code:

# ../glibc-2.4/configure --prefix=/usr/local/glibc2.4 --enable-addons=linuxthreads --without-tls;
I added --without-tls to ./configure and now attempting to comple again, maybe it'll work now... I'll report on that later. (UPDATE... still failed with same message.. should I take out "--enable-addons=linuxthreads" ? UPDATE AGAIN... still no go.)

Quote:

Originally Posted by sundialsvcs
Glibc is special. Glibc is different. :eek: Attempting to update glibc without knowing what you are doing can render your system inoperable! :eek:

Generally, glibc is updated only as part of the process of installing a completely new distribution on the machine, or a completely new release of the same. I advise you to do likewise.

Here's why: of all of the shared libraries on your system, glibc is used by nearly all programs on your system, including ones (like init, or basic commands) without which your system cannot run or cannot be used. If you botch the update, there's no easy way to get back out.

This is why I'm using --prefix=/usr/local/glibc2.4

I understand this is the safest way without compromising anything (since it's in it's own self contained dir.) Basically parallel glibc.

I'm thinking of leaving gcc 2.96 for compiling things against the old glibc 2.2.5-44 (original from RPM), and dedicating gcc 4.1.1 for the newer compiles using glibc 2.4, if I can get it compiled.

Any comments on that are more than welcome.


Quote:

Been there... http://www.linuxfromscratch.org... done that... screwed it up once :rolleyes: ... okay, make that twice ... finally did it. Don't do it.
I just think it's much safer installing it with --prefix :)

Also, why doesn't anyone ever mention running a new glibc in parallel in replies to questions about upgrding glibc?


All times are GMT -5. The time now is 10:01 PM.