SEO

Hello,

I followed the Gentoo guide when I upgraded my GCC 3.4 to 4.1, but I ran
into a problem when emerge -eav world was getting processed.

This caused over 700 packages to be re-emerged, and somewhere in the
numbers of 400 blas-atlas (or lapack-atlas, I can't remember :-) refused
to be configured automatically, so I had to do this manually, with
success, but then emerge --resume wanted to start with last package, so
I would have the same problem again.

Then I tried to run emerge -DutNav world, but this only wanted to
upgrade a few packages.

emerge -eav world on the other hand wants to do the whole bunch again.

Does this situation look dangerous to anyone or can I just ignore this.

And what is the fundamental difference between the normal upgrade I run
from time to time (-Dun/DutNav) and the emptytree way?

Thanks,

Wimmy

--
Being owned by someone used to be called slavery.
Now it's called commitment.

Wim Cossement wrote:
> Hello,
>
> I followed the Gentoo guide when I upgraded my GCC 3.4 to 4.1, but I ran
> into a problem when emerge -eav world was getting processed.
>
> This caused over 700 packages to be re-emerged, and somewhere in the
> numbers of 400 blas-atlas (or lapack-atlas, I can't remember :-) refused
> to be configured automatically, so I had to do this manually, with
> success, but then emerge --resume wanted to start with last package, so
> I would have the same problem again.
>
> Then I tried to run emerge -DutNav world, but this only wanted to
> upgrade a few packages.
>
> emerge -eav world on the other hand wants to do the whole bunch again.
>
> Does this situation look dangerous to anyone or can I just ignore this.
>
> And what is the fundamental difference between the normal upgrade I run
> from time to time (-Dun/DutNav) and the emptytree way?
>
> Thanks,
>
> Wimmy

PS: I've ran revdep-rebuild to check for any broken libs and fix them
(since it found a few)!

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Wim Cossement said the following on 01/05/2007 03:47 PM:
| Hello,
|
| I followed the Gentoo guide when I upgraded my GCC 3.4 to 4.1, but I ran
| into a problem when emerge -eav world was getting processed.
|
| This caused over 700 packages to be re-emerged, and somewhere in the
| numbers of 400 blas-atlas (or lapack-atlas, I can't remember :-) refused
| to be configured automatically, so I had to do this manually, with
| success, but then emerge --resume wanted to start with last package, so
| I would have the same problem again.
|
| Then I tried to run emerge -DutNav world, but this only wanted to
| upgrade a few packages.
|
| emerge -eav world on the other hand wants to do the whole bunch again.
|
| Does this situation look dangerous to anyone or can I just ignore this.
|
| And what is the fundamental difference between the normal upgrade I run
| from time to time (-Dun/DutNav) and the emptytree way?
|
| Thanks,
|
| Wimmy
|

- --emtytree just ignores, that any packages are installed. So with
running emerge -eav world, you do the same, you're doing with running
emerge -av {all installed packages} on a fresh system.
Thats why it "wants to do the whole bunch again."

It is generally better to run an emerge -eav after a gcc-upgrade, since
there were ABI changes, so every programm, written in c++ _will_ have
problems, but there are many packages that simply don't use c++.
So I just ommited this step. You should at least do an emerge -eav
system (but that may have been done within the first 400 packages of
your emerge -eav world). And if you experience crashes, just remerge the
affected package.

Be careful, if you're using kde. Kde and qt are completely based on c++.

- --
*Sebastian Volke*
registered Linux user #426550

mail address: echo ozslxhmfw_gfxyn@lrc.sjy | perl -pe 'y/a-z/v-za-w/'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFnqGcTVzZ9whcz3sRAuSVAKCrLlRQOLHcTv9r0CbU6L ajV3Mk6ACeOJXh
lmO9EgU3OTH5Q8oZx9dqIYA=
=DRNf
-----END PGP SIGNATURE-----

Wim Cossement <wcosseme@nospam.bcol.be> wrote:
> Hello,
>
> I followed the Gentoo guide when I upgraded my GCC 3.4 to 4.1, but I
> ran into a problem when emerge -eav world was getting processed.
>
> This caused over 700 packages to be re-emerged, and somewhere in the
> numbers of 400 blas-atlas (or lapack-atlas, I can't remember :-)
> refused to be configured automatically, so I had to do this manually,
> with success, but then emerge --resume wanted to start with last
> package, so I would have the same problem again.

It's too late now, but you should probably have tried:
emerge --skipfirst --resume

Regards,
--
*Art

Arthur Hagen wrote:
> Wim Cossement <wcosseme@nospam.bcol.be> wrote:
>> Hello,
>>
>> I followed the Gentoo guide when I upgraded my GCC 3.4 to 4.1, but I
>> ran into a problem when emerge -eav world was getting processed.
>>
>> This caused over 700 packages to be re-emerged, and somewhere in the
>> numbers of 400 blas-atlas (or lapack-atlas, I can't remember :-)
>> refused to be configured automatically, so I had to do this manually,
>> with success, but then emerge --resume wanted to start with last
>> package, so I would have the same problem again.
>
> It's too late now, but you should probably have tried:
> emerge --skipfirst --resume
>
> Regards,

Aha, I was hoping for a way to ignore a failed packages!

Thanks for the tip!

But I'll just rerun the emerge -eav world since revdep-rebuild still
gives missing libs but does not propose any more candidates for
re-emerging. Strange, eh?

Wimmy

--
Being owned by someone used to be called slavery.
Now it's called commitment.

Wim Cossement wrote:
> Hello,
>
> I followed the Gentoo guide when I upgraded my GCC 3.4 to 4.1, but I ran
> into a problem when emerge -eav world was getting processed.
>
> This caused over 700 packages to be re-emerged, and somewhere in the
> numbers of 400 blas-atlas (or lapack-atlas, I can't remember :-) refused
> to be configured automatically, so I had to do this manually, with
> success, but then emerge --resume wanted to start with last package, so
> I would have the same problem again.
>
> Then I tried to run emerge -DutNav world, but this only wanted to
> upgrade a few packages.
>
> emerge -eav world on the other hand wants to do the whole bunch again.
>
> Does this situation look dangerous to anyone or can I just ignore this.
>
> And what is the fundamental difference between the normal upgrade I run
> from time to time (-Dun/DutNav) and the emptytree way?
>
> Thanks,
>
> Wimmy
>

I've just noticed a few precompiled apps that I installed however still
need stdlibc++.so.5 instead of the new stdlibc++.so.6 so I guess I still
have to leave gcc-3.4.6 on there.

But doesn't it change the libpaths when switching to the 4.1.1? So
perhaps just emerging is not enough?

I'm kinda a dumbass on this matter...

Wimmy

On Mon, 8 Jan 2007, Wim Cossement wrote:

> Wim Cossement wrote:
>
> I've just noticed a few precompiled apps that I installed however still need
> stdlibc++.so.5 instead of the new stdlibc++.so.6 so I guess I still have to
> leave gcc-3.4.6 on there.

Take a look at the package sys-libs/libstdc++-v3-3.3.4

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Wim Cossement said the following on 01/08/2007 04:55 PM:

| I've just noticed a few precompiled apps that I installed however still
| need stdlibc++.so.5 instead of the new stdlibc++.so.6 so I guess I still
| have to leave gcc-3.4.6 on there.
|
| But doesn't it change the libpaths when switching to the 4.1.1? So
| perhaps just emerging is not enough?
|
| I'm kinda a dumbass on this matter...
|
AFAIK, you only have to use gcc-config to set your system's gcc version
to 4.1.1. If you've followed the Gentoo GCC upgrading guide, you've done
that already.

- --
*Sebastian Volke*
registered Linux user #426550

mail address: echo ozslxhmfw_gfxyn@lrc.sjy | perl -pe 'y/a-z/v-za-w/'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFo8iYTVzZ9whcz3sRAhYAAJoDN+OmPyq//HhaTC5sPdLBCBXM3wCbBRs0
KvXpTcTTkEF0xl0Hs8zJuU4=
=3URF
-----END PGP SIGNATURE-----