From: Alec Warner <warnera6@egr.msu.edu>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Automatically replace -mtune= with -mcpu= if not supported by gcc?!
Date: Sun, 17 Apr 2005 18:24:04 -0400 [thread overview]
Message-ID: <4262E204.1090000@egr.msu.edu> (raw)
In-Reply-To: <200504171805.53333.vapier@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Mike Frysinger wrote:
> On Sunday 17 April 2005 09:50 am, Philipp Hasse wrote:
>
>>This way it can be used to set the -mcpu and -mtune flags correctly.
>
>
> not worth the added crap imho
> -mike
Better to have it fail and have the users fix their build-env themselves.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iQIVAwUBQmLiA2zglR5RwbyYAQKtxhAAj75Fcnr/eEtdaJs6bg9IGpR6bVwQG0EU
n698FfVxeZrTyCuEoKgZZ3QpayAQB3QwjH+NuYn0DrgNaFFc0RRUBn21eNMe5P/q
ygm7u97N1ROk9142vj/HCj12AkqEMIE1eEIOAe2OEKtWCR0OlBmLF3lJLtb/TZ1M
XrdzU+hTf01NE0hjksBkm5V6cEvcxEHOmAXbijSzv2iabedidbFW1oNGqyniHbVb
NNpgfqY67JiielA8UkDSDHg/FNXxL47R76b0KK/CUc+wY/t7KdR7B7g/z1iLpM/N
vOrPbRtLw21xF0gKPsIIKKybE8f5N+gnCVjVIwoWvse6kCbpzWHff1E5HLzVDtyc
HeERmqH36PcCF3IcthBi4rSV2dIl4K5IFNTOpX1y64Nv7McAkX73Hx5TU7+1YlPf
LNF7+ZVK/32zf9VUFGmpWEu4ofULb1wmh4xy+dOIKnoDVUO3yKFitZ+3zArTapSB
d6IaiEglhkYPHx9GBdtgwxADqBsgn1ASidWDaYmiuKGVsthKJY671gVZdIyphwSK
lf7uG1rgatDyfigg2U5YExN5TRupz1fj/NwVX8htvYGpFuZwCo+eQx9+N1gEiCrj
2FNr6IlEosqEiS5Ki7HGcb7VvH4Bbn+PRK2u1gd9r0DpGY+zfJxtTru+fYzG9+nR
rn+6NNPEpWQ=
=Z9eL
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-04-17 22:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 13:50 [gentoo-dev] Automatically replace -mtune= with -mcpu= if not supported by gcc?! Philipp Hasse
2005-04-17 22:05 ` Mike Frysinger
2005-04-17 22:24 ` Alec Warner [this message]
2005-04-19 19:42 ` Paul de Vrieze
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4262E204.1090000@egr.msu.edu \
--to=warnera6@egr.msu.edu \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox