| 1 |
On Saturday 25 September 2004 09:39, Mike Frysinger wrote: |
| 2 |
> just a heads up but ive changed the order of arguements for the |
| 3 |
> replace-cpu-flags ... |
| 4 |
> |
| 5 |
> old method: replace-cpu-flags <new cpu> <old cpus> |
| 6 |
> new method: replace-cpu-flags <old cpus> <new cpu> |
| 7 |
> |
| 8 |
> yeah, it sucks, but it's to go along with the standard of all the other |
| 9 |
> replace functions in flag-o-matic (see Bug #60597) |
| 10 |
|
| 11 |
To this respect it might be nice to have default replaces based on the |
| 12 |
compiler version. I have an amd64, but when I tried to compile gcc-3.3 it |
| 13 |
broke because (obviously) gcc-3.3 does not know -march=athlon64. A |
| 14 |
replace-cpu flags statement in the package could have fixed it, but I suspect |
| 15 |
that there are more places where this could come in handy. |
| 16 |
|
| 17 |
Paul |
| 18 |
|
| 19 |
-- |
| 20 |
Paul de Vrieze |
| 21 |
Gentoo Developer |
| 22 |
Mail: pauldv@g.o |
| 23 |
Homepage: http://www.devrieze.net |
Archives