Switching march from Pentium2 to Pentium3 [Solved]

[linuxtuxhellsinki]

So I was moving my HD from my old ThinkPad PII 300Mhz to HP PIII 500Mhz and now I thought should I do emerge -e sytem && emerge -e world to take advance of my new cpu's features (march=pentium3, sse +?)

Or should I just compile the affected packets ?

[massimo]

I would suggest compiling the whole system with your new -march.
_________________
Hello 911? How are you?

[linuxtuxhellsinki]

Yeah I thought so too and was almost doing it, but then I was thinking that is it necessary and asking it from here is the best way to find out it (the best forums of the world)

So how should I do it in the correct way ? Should I first compile the toolchain (binutils, gcc, glibc and what else and in which order ?) and then system & world And is there some other USE-flags or Cflags which I should add

[Donman]

You should be prepared to encounter with -fvisibility-inlines-hidden. A few packages will bomb out while using it. Same with -fvisibility=hidden. All in all, its up to you. Other than that, you should not need to add any more *FLAGS. And if you are just getting the system optimized to your new processor, a simple emerge -e world should suffice. But IMHO, two emerge -e world's would be better. But maybe thats cause I'm just a crazy man that worries alot...

**Edit**: If you do experience breakage with -fvisibility*, then you can use this nifty bashrc. It'll let you set up per package CFLAGS and such. Use that instead of Bugzilla.

[linuxtuxhellsinki]

Yes, I've realized that some packages are not building with -fvisibility=hidden and if that happens I've just commented that part away for a while CXXFLAGS="${CFLAGS}"# -fvisibility=hidden -fvisibility-inlines-hidden" ,but that portage-bashrc-ng seems like the right tool for these situations. Thanks

I started this 'upgrading' last night with compiling the toolchain and now I'm in middle of emerging the system. Let's see how long it's gonna take, but it feels like this is quite much faster than my old PII, which you can see from this...

[linuxtuxhellsinki]

Now I've a problem after the emerge -eav system , cause now when I'm going to update world in the same way, it wants to build all those system packages cause they also belong to world.

So how can I prevent it ? Is the only way to stop all the system packages and emerge --resume --skipfirst then


Edit : And now I've just deleted all the distfiles, so it wants to dl 'em again
_________________
1st use 'Search' & lastly add [Solved] to
the subject of your first post in the thread.

[massimo]

[psyqil]

[linuxtuxhellsinki]

Thanks for that info, but I already checked which were in the system (~100pkgs) from the list which I've copy/pasted to the file. Then I just interrupted those 100 first packages and "--resume --skipfirst":ed 'em and now it's compiling 4th of 689 packages of the world.


psyqil : I was trying to find that looong "An emerge wrapper for more correctly building the toolchain" thread with some 'toolchain' etc. searchwords (cause I couldn't remember the name of that thread) but with no sucess. Maybe I've time to read it this time to the end

I'll add [solved] to this thread, but if someone can give some other tips for this P2-P3 conversion that would be nice to hear, like are there some other use-flags, progs... which could be useful for performance wise (prelink ?).
Here's my cpuinfo, is this some kind of mobile-cpu which could scale frequencies (I readed that from somewhere)

[psyqil]