View previous topic :: View next topic |
Author |
Message |
whaase n00b
Joined: 20 Nov 2003 Posts: 69
|
Posted: Sun Nov 30, 2003 7:55 pm Post subject: Am I doing this right? |
|
|
I started with the stage2 from the i686 directory on the gentoo server. I unpacked that and edited the make.conf file. I changed the following:
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=athlon -O3 -pipe -fomit-frame-pointer"
CXXFLAGS="-march=athlon -O3 -pipe -fomit-frame-pointer"
In the docs it says not to change the CHOST flag if you are not doing the stage1. But it didn't really say anything about the CFLAGS and CXXFLAGS. Will I be ok with doing this?
Walter |
|
Back to top |
|
|
joem Retired Dev
Joined: 20 Dec 2002 Posts: 508 Location: Bloomington, In
|
Posted: Sun Nov 30, 2003 8:42 pm Post subject: |
|
|
as long as you have an athalon processor, those are fine flags. |
|
Back to top |
|
|
whaase n00b
Joined: 20 Nov 2003 Posts: 69
|
Posted: Sun Nov 30, 2003 8:54 pm Post subject: |
|
|
dst wrote: | as long as you have an athalon processor, those are fine flags. |
Thanks, Duron
Walter |
|
Back to top |
|
|
whaase n00b
Joined: 20 Nov 2003 Posts: 69
|
Posted: Mon Dec 01, 2003 4:02 pm Post subject: |
|
|
Just for the record, it didn't work. I got multiple compile errors while installing stage 2. I guess I'll do 1 of 2 things. Either install from stage1 or just leave the flags as they are for a i686....
Walter |
|
Back to top |
|
|
deprecated Tux's lil' helper
Joined: 21 Aug 2002 Posts: 118 Location: Madison, WI
|
Posted: Mon Dec 01, 2003 5:07 pm Post subject: |
|
|
Note that is is VERY important to not change the CHOST flag.
However, in theory you should have been fine with changing the cflags.
The cflags will only affect things you compile after you set the cflags. Essentially the programs that come compiled in the stage 2 will not get any optimizations from your cflags unless you re-compile them.
If it errored out, its possible that one of the programs you were compiling was incompatible with one of the cflags you set. In most cases, if something errors out you can simply reduce the optimization settings for that one package until you figure out which one causes the death of the compile. The amount of time you want to spend messing with stuff like this might not be so great, I highly recommend using -Os instead of -O3, it seems much less error prone and the timings I've seen are on par with O3.
Or if the error wasn't related to compiling, please post it in a new thread.
-Dep |
|
Back to top |
|
|
whaase n00b
Joined: 20 Nov 2003 Posts: 69
|
Posted: Mon Dec 01, 2003 5:57 pm Post subject: |
|
|
deprecated wrote: | Note that is is VERY important to not change the CHOST flag.
However, in theory you should have been fine with changing the cflags.
The cflags will only affect things you compile after you set the cflags. Essentially the programs that come compiled in the stage 2 will not get any optimizations from your cflags unless you re-compile them.
If it errored out, its possible that one of the programs you were compiling was incompatible with one of the cflags you set. In most cases, if something errors out you can simply reduce the optimization settings for that one package until you figure out which one causes the death of the compile. The amount of time you want to spend messing with stuff like this might not be so great, I highly recommend using -Os instead of -O3, it seems much less error prone and the timings I've seen are on par with O3.
Or if the error wasn't related to compiling, please post it in a new thread.
-Dep |
I'm going to try a stage1 install. I will use the -Os instead of -O3. I was reading a bit about it. I'll post how it goes.
Walter |
|
Back to top |
|
|
|