[gentoo-user] Update to glibc-2.4-r3 with gcc-3.4.6

[gentoo-user] Update to glibc-2.4-r3 with gcc-3.4.6

[Remy Blank]

Has anybody tried updating glibc to the latest stable 2.4-r3, but
without also updating gcc to 4.1.1? Any problems?

>From the ebuild, >=sys-devel/gcc-3.4.4 should be supported.

I'd like to do the updates separately if possible.

Thanks.
-- Remy


Remove underscore and suffix in reply address for a timely response.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Update to glibc-2.4-r3 with gcc-3.4.6

[David Grant]

[-- Attachment #1: Type: text/plain, Size: 870 bytes --]

I did and I totally screwed up my system. I managed to fix it eventually by
booting to a live CD and untaring the quickpkg I made into the / directory.

I might have done something wrong to cause this but I'm not sure what it
was. Anyways, make sure you do quickpkg before hand, and secondly, don't do
it until you get some responses back from others who did it succesfully.

Dave

On 9/15/06, Remy Blank <remy.blank_asps@pobox.com> wrote:
>
> Has anybody tried updating glibc to the latest stable 2.4-r3, but
> without also updating gcc to 4.1.1? Any problems?
>
> From the ebuild, >=sys-devel/gcc-3.4.4 should be supported.
>
> I'd like to do the updates separately if possible.
>
> Thanks.
> -- Remy
>
>
> Remove underscore and suffix in reply address for a timely response.
>
> --
> gentoo-user@gentoo.org mailing list
>
>


-- 
David Grant
http://www.davidgrant.ca

[-- Attachment #2: Type: text/html, Size: 1295 bytes --]

[gentoo-user] Re: Update to glibc-2.4-r3 with gcc-3.4.6

[Remy Blank]

David Grant wrote:
> I did and I totally screwed up my system. I managed to fix it eventually
> by booting to a live CD and untaring the quickpkg I made into the /
> directory.

Yes, I saw your posts on bug 125868 [1].

> ... and secondly, don't
> do it until you get some responses back from others who did it succesfully.

Well, I did it anyway (had a bit of time on my hands). And surprise, I
had the exact same symptoms as the bug above, i.e. a relocation error
before unmerging the previous glibc-2.3.6-r4. But everything was still
working ok.

So I did *not* panic ;-) and just emerged glibc-2.4-r3 a second time (I
had made a binary package, so this was quite fast), and this time the
previous glibc was unmerged correctly. I suppose an emerge --prune would
also have worked. Your problem was most likely due to your having
unmerged glibc-2.4, which left you with a system without glibc.

So there does seem to be a bug, albeit not really a critical one, in the
merge process. But it can be fixed easily by unmerging the *old* glibc
version.

-- Remy

[1] http://bugs.gentoo.org/show_bug.cgi?id=125868

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Re: Update to glibc-2.4-r3 with gcc-3.4.6

[David Grant]

[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]

On 9/15/06, Remy Blank <remy.blank_asps@pobox.com> wrote:
>
> David Grant wrote:
> > I did and I totally screwed up my system. I managed to fix it eventually
> > by booting to a live CD and untaring the quickpkg I made into the /
> > directory.
>
> Yes, I saw your posts on bug 125868 [1].
>
> > ... and secondly, don't
> > do it until you get some responses back from others who did it
> succesfully.
>
> Well, I did it anyway (had a bit of time on my hands). And surprise, I
> had the exact same symptoms as the bug above, i.e. a relocation error
> before unmerging the previous glibc-2.3.6-r4. But everything was still
> working ok.
>
> So I did *not* panic ;-) and just emerged glibc-2.4-r3 a second time (I
> had made a binary package, so this was quite fast), and this time the
> previous glibc was unmerged correctly. I suppose an emerge --prune would
> also have worked. Your problem was most likely due to your having
> unmerged glibc-2.4, which left you with a system without glibc.


Is that what I said I did in the bug report? Ok, I did do something wrong.
:-) Well for my MythTV box (the one I screwed up) I'll be waiting probably 6
months to a year to upgrade just to make sure there are no problems.
Actually I'll probably just leave the new glibc and gcc hard-masked until I
am forced to upgrade due to the old one being removed from portage or due to
a dependancy.

-- 
David Grant
http://www.davidgrant.ca

[-- Attachment #2: Type: text/html, Size: 1816 bytes --]