* [gentoo-dev] swapping order of arguements for replace-cpu-flags
@ 2004-09-25 7:39 Mike Frysinger
2004-09-25 14:52 ` Paul de Vrieze
0 siblings, 1 reply; 3+ messages in thread
From: Mike Frysinger @ 2004-09-25 7:39 UTC (permalink / raw
To: gentoo-dev
just a heads up but ive changed the order of arguements for the
replace-cpu-flags ...
old method: replace-cpu-flags <new cpu> <old cpus>
new method: replace-cpu-flags <old cpus> <new cpu>
yeah, it sucks, but it's to go along with the standard of all the other
replace functions in flag-o-matic (see Bug #60597)
i've gone ahead and fixed all affected ebuilds
-mike
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [gentoo-dev] swapping order of arguements for replace-cpu-flags
2004-09-25 7:39 [gentoo-dev] swapping order of arguements for replace-cpu-flags Mike Frysinger
@ 2004-09-25 14:52 ` Paul de Vrieze
2004-09-26 4:30 ` Mike Frysinger
0 siblings, 1 reply; 3+ messages in thread
From: Paul de Vrieze @ 2004-09-25 14:52 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 864 bytes --]
On Saturday 25 September 2004 09:39, Mike Frysinger wrote:
> just a heads up but ive changed the order of arguements for the
> replace-cpu-flags ...
>
> old method: replace-cpu-flags <new cpu> <old cpus>
> new method: replace-cpu-flags <old cpus> <new cpu>
>
> yeah, it sucks, but it's to go along with the standard of all the other
> replace functions in flag-o-matic (see Bug #60597)
To this respect it might be nice to have default replaces based on the
compiler version. I have an amd64, but when I tried to compile gcc-3.3 it
broke because (obviously) gcc-3.3 does not know -march=athlon64. A
replace-cpu flags statement in the package could have fixed it, but I suspect
that there are more places where this could come in handy.
Paul
--
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [gentoo-dev] swapping order of arguements for replace-cpu-flags
2004-09-25 14:52 ` Paul de Vrieze
@ 2004-09-26 4:30 ` Mike Frysinger
0 siblings, 0 replies; 3+ messages in thread
From: Mike Frysinger @ 2004-09-26 4:30 UTC (permalink / raw
To: gentoo-dev
On Saturday 25 September 2004 10:52 am, Paul de Vrieze wrote:
> To this respect it might be nice to have default replaces based on the
> compiler version. I have an amd64, but when I tried to compile gcc-3.3 it
> broke because (obviously) gcc-3.3 does not know -march=athlon64. A
> replace-cpu flags statement in the package could have fixed it, but I
> suspect that there are more places where this could come in handy.
what you're asking for (while a good point) is outside the scope of
replace-cpu-flags ...
-mike
--
gentoo-dev@gentoo.org mailing list
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-09-26 4:30 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-09-25 7:39 [gentoo-dev] swapping order of arguements for replace-cpu-flags Mike Frysinger
2004-09-25 14:52 ` Paul de Vrieze
2004-09-26 4:30 ` Mike Frysinger
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox