Gentoo USE flags?

[Boris27]

I've finished building a stage3 gentoo system on a ahtlon 1100 (my bro's pc), and now I'm eager to install gentoo on my PC too... I'd like to do stage1.
What use flags should I set? I want to use KDE, and I'd like to game, as far as that is possible on this Radeon 9100....

I've already set -march=athlon-xp. What else should I set for optimal performance?

My pc is a Amd Athlon 2500+ (barton core) on a Abit NF7-S (nForce2) with 512 megs of DDR..
Im planning to overclock it for the setup, as to save some time. I know what settings are stable (200x11 is stable).

TIA.

[panther]

Check

www.freehackers.org


they have a nice set of flags for all the processors

[louiscypher]

There's a CCFLAGS nofomit (sp?) option which will really increase the speed of your desktop on Gentoo.

(Sorry, it's off the top of my head from an install 2 months ago, first time was a dog, so I started hacking, worked superbly until I started monkeying around with virtual mail servers.)

[je_fro]

I have that same processor and MoBo. My flags are:
USE="X gtk gtk2 -gnome -arts moznoirc moznomail cups pda ssl tcpd kde alsa aavm 3dnow mmx"

CHOST="i686-pc-linux-gnu"

CFLAGS="-march=athlon-xp -O3 -pipe"

CXXFLAGS="${CFLAGS}"

Let me know if you have any trouble.

[Boris27]

Originally posted by je_fro
I have that same processor and MoBo. My flags are:
USE="X gtk gtk2 -gnome -arts moznoirc moznomail cups pda ssl tcpd kde alsa aavm 3dnow mmx"

CHOST="i686-pc-linux-gnu"

CFLAGS="-march=athlon-xp -O3 -pipe"

CXXFLAGS="${CFLAGS}"

Let me know if you have any trouble.

I used -fomit-frame-pointer in my CFLAGS too, got it from that freehackers site. Thanks though, the USE flags came in handy :)

[Hayl]

don't use -O3, it makes bloated (large) binaries that (in most cases) do not run any faster and in all cases are larger (take longer to load). use -O2 or -Os instead.

-Os gives you the smallest possible binaries, i.e. doesn't use any optimizations that make the binaries larger

-O2 gives you optimized binaries that are slightly larger than -Os, so they will likely run faster but will take slightly longer to load

[Boris27]

Originally posted by Hayl
don't use -O3, it makes bloated (large) binaries that (in most cases) do not run any faster and in all cases are larger (take longer to load). use -O2 or -Os instead.

-Os gives you the smallest possible binaries, i.e. doesn't use any optimizations that make the binaries larger

-O2 gives you optimized binaries that are slightly larger than -Os, so they will likely run faster but will take slightly longer to load

-O2 it is then :)