SEO

#1 (**permalink**) 02-21-2008, 06:15 AM

output from "emerge --verbose arts":
http://members.shaw.ca/anthonyr/emerge_arts
output from "emerge --verbose --info args":
http://members.shaw.ca/anthonyr/emerge_info_arts

I've done a stage 1 install, and I'm just getting up to kde now. I've
done a bunch of stuff that uses C++ like Mozilla, and that all worked
but I did an "emerge -u world" before I tried KDE, and it installed a
new version of glibc, so I think that might be the cause of the problem.

I'm kinda new to Gentoo so forgive me if I've forgotten information.

TIA for any help,
Anthony

#2 (**permalink**) 02-21-2008, 06:15 AM

Anthony Roberts wrote:

> output from "emerge --verbose arts":
> http://members.shaw.ca/anthonyr/emerge_arts
> output from "emerge --verbose --info args":
> http://members.shaw.ca/anthonyr/emerge_info_arts
>
> I've done a stage 1 install, and I'm just getting up to kde now. I've
> done a bunch of stuff that uses C++ like Mozilla, and that all worked
> but I did an "emerge -u world" before I tried KDE, and it installed a
> new version of glibc, so I think that might be the cause of the problem.
>
> I'm kinda new to Gentoo so forgive me if I've forgotten information.
>

Now do an emerge sync, emerge portage, emerge -u gcc, emerge -u glibc (just
in case) run etc-update after any updates. emerge -ep world to check for
blocking packages - note any down then remove them.

Now for the fun part: emerge -e world.
This will recompile everything with the gcc, glibc that you just got. This
should take all night.

Having done that your system will probably be much more stable and fast as
well.

Styvaen.

#3 (**permalink**) 02-21-2008, 06:15 AM

> Now do an emerge sync, emerge portage, emerge -u gcc, emerge -u glibc (just
> in case) run etc-update after any updates. emerge -ep world to check for
> blocking packages - note any down then remove them.

The version of glibc that it wants to install is the one that broke
arts, so I'm not going to. Going back to the old version of glibc
(2.3.2-r2) fixed it, so I'm not going to update to the same version that
broke it.

> Now for the fun part: emerge -e world.
> This will recompile everything with the gcc, glibc that you just got. This
> should take all night.

wait-- wouldn't I want to recompile gcc with the new copy of glibc
already there?

I'm on the most current gcc anyway...

#4 (**permalink**) 02-21-2008, 06:16 AM

Anthony Roberts wrote:

>
> wait-- wouldn't I want to recompile gcc with the new copy of glibc
> already there?
>
> I'm on the most current gcc anyway...

Yes after compiling the new gcc you would want to use that for glibc before
recompiling gcc with the new gcc linked against new glibc.

It's funny but as I was going to work I was thinking about this very
problem. Which do you merge first. I concluded that if you merged glibc
first then you would wan't to compile them both twice in alternating order.

Has anyone ever tried to update with both methods to compare the resulting
binaries? No, I can't be bothered myself.

Styvaen.

#5 (**permalink**) 02-21-2008, 06:17 AM

I caved, I'm rebuilding just so I'm sure I know how, as I haven't done
it before.

I gotta say, I'm happier with a P4 2.4G than I was with a Cel 2G. The
cache makes a huge difference. Hyperthreading slows it down, but that
can be adjusted as necessary.

> Yes after compiling the new gcc you would want to use that for glibc before
> recompiling gcc with the new gcc linked against new glibc.

Looking at `emerge -ep world`, it looks like it does both more than once
anyway, but I did it a few extra times anyway just to be sure. I had to
study, and I wasn't ready for world yet, so it wasn't any extra trouble.

#6 (**permalink**) 02-21-2008, 06:17 AM

Anthony Roberts wrote:

> I caved, I'm rebuilding just so I'm sure I know how, as I haven't done
> it before.
>
> I gotta say, I'm happier with a P4 2.4G than I was with a Cel 2G. The
> cache makes a huge difference. Hyperthreading slows it down, but that
> can be adjusted as necessary.
>
>> Yes after compiling the new gcc you would want to use that for glibc
>> before recompiling gcc with the new gcc linked against new glibc.
>
> Looking at `emerge -ep world`, it looks like it does both more than once
> anyway, but I did it a few extra times anyway just to be sure. I had to
> study, and I wasn't ready for world yet, so it wasn't any extra trouble.

I am having trouble getting world to recompile. I think I will try system
tonight and see if that goes ok then I will try recompiling world again
tomorrow.

It fails on the arts build and comes out with a load of nvidia opengl
symbols not being relocatable or something.

I may end up having to temporarily unmerge kde in order to get world to
recompile.

Styvaen.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

kde fails on arts