gcc-4.6.3 reinstalling 3 times in a weeks time?

padoor · Advocate Joined: 30 Dec 2005 Posts: 4185 Location: india

in the last week and today gcc-4.6.3 is being reinstalled 4th time.
how so? again useflags changes??
_________________
reach out a little bit more to catch it (DON'T BELIEVE the advocate part under my user name)

Veldrin · Posted: Thu Jan 24, 2013 8:44 am Post subject:

What command are you using to upgrade?
What is the error message?

Did you change anything recently?

There was an udev upgrade, which might or might not force a gcc rebuild - at least the suggest command after the udev upgrade did in my case.
_________________
read the portage output!
If my answer is too concise, ask for an explanation.

padoor · Advocate Joined: 30 Dec 2005 Posts: 4185 Location: india

i use emerge -DNuav world
last week wine and gcc were upgraded.
next day both were reinstalled.
then again next day gcc was reinstalled.
today againg gcc reinstalled.
i dont know what called all reinstalls.
a lot of packages upgraded about 75 of them
there is no error all 4 times gcc merged correctly.
i am now using gcc-4.6.3
_________________
reach out a little bit more to catch it (DON'T BELIEVE the advocate part under my user name)

Veldrin · Posted: Thu Jan 24, 2013 11:22 am Post subject:

leifbk · Posted: Thu Jan 24, 2013 11:58 am Post subject:

I have noticed the same, simply as a result of running emerge --sync && emerge -avuDN world every morning. It's because of a few changes in use flags. They could probably have been better coordinated, but this is happening all the time. Because gcc is a monster package compared to most others, it can be a little annoying, though. But the decision to sync and update every day is your own.
_________________
Grumpy old man

juantxorena · Posted: Sat Jan 26, 2013 10:37 am Post subject:

It's 4 times now. Somebody should open a bug.

I remember having similar problems with the now extint blas-atlas and lapack-atlas packages. Some devs were fighting over some USE flag, whether it should be on by default or not, so they kept changing them. The problem was that those packages requiered some pre and post emerge stuff (disabling CPU throttling, for example) and they needed over 2 hours of compile time no matter the CPU since they had to do a lot of tests to optimize stuff. They didn't stop until somebody (me) opened a bug complaining.

This gcc thing looks the same to me.
_________________
I cannot write English very well. Please, correct any mistake so that I can improve.

Anon-E-moose · Posted: Sat Jan 26, 2013 10:44 am Post subject:

take 'N' out of the flags

ie. use -avuD instead of -avuDN

asturm · Posted: Sat Jan 26, 2013 10:53 am Post subject:

Easy. Don't use -N on a permanent basis, it's useless.

Wait, didn't I already tell you that some time ago?
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic

ppurka · Advocate Joined: 26 Dec 2004 Posts: 3247

I use "-auDv --changed-use". It will get recompiled only if needed.

asturm · Posted: Sun Feb 10, 2013 10:31 am Post subject:

I just had a look again at my emerge -uvaDN world output after the profile update. Out of 26 reinstalls more than 20 would have been completely useless waste of cpu time, because of disappearing, renamed or language flags that I didn't use at all. 4 packages of those I did re-emerge manually for the slightest chance of actual change in install size.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic