1 |
So what about: |
2 |
1. setting optimizations in make.conf and elsewehre for the *final* paltform |
3 |
2. bootstrap; emerge -b gcc |
4 |
3. change optimizations to what you would like to have temporarily for gcc |
5 |
4. emerge gcc |
6 |
5. switch optimizations back |
7 |
6. emerge the rest |
8 |
7. emerge --usepkg gcc (or just emerge it here skipping 2) |
9 |
This way you should get your packages built with correct settings and may |
10 |
enjoy gcc optimized for athlon while building them (although I am not sure |
11 |
you will save much in terms of time this way. I eman versus using i486 |
12 |
optimized gcc). Just be carefull about having the right version of gcc in the |
13 |
end.. |
14 |
|
15 |
George |
16 |
|
17 |
|
18 |
On Sunday 05 January 2003 21:12, Arnold deVos wrote: |
19 |
> Nope, as explained earlier in the thread that wouldn't get the benefits of |
20 |
> having gcc optimized for the athlon. It would not work at all to build |
21 |
> packages for an incompatible arch such as P4. |
22 |
> |
23 |
> - Arnold |
24 |
|
25 |
|
26 |
-- |
27 |
gentoo-dev@g.o mailing list |