From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] which -march flag to pick for Intel Core 2 Duo in make.conf?
Date: Thu, 24 May 2007 16:43:10 +0100 [thread overview]
Message-ID: <20070524164310.46a03922@zaphod.digimed.co.uk> (raw)
In-Reply-To: <d9a0a6da0705240813j3e2121sf112e31f37437ceb@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]
On Thu, 24 May 2007 11:13:30 -0400, Denis wrote:
> After reading some docs, the impression I get is that the 'nocona'
> flag is for building a 64-bit system... For a 32-bit system, it seems
> like 'prescott' would be the choice, wouldn't it?
Yes.
> We don't have gcc-4.2.0 in our portage available for installation yet,
> do we? Anyone know when?
When the devs consider it suitable for at least the testing branch or
when you do "echo =sys-devel/gcc-4.2*" >>/etc/portage/package.mask,
whichever comes sooner.
Bear in mind that GCC is almost certainly masked for good reason. It's
not like you're using a binary distro and only need a compiler for a few
packages. Feel free to try it in the knowledge that if it breaks your
system, you get to keep the pieces.
--
Neil Bothwick
Sects, sects, sects, is that all you monks think about?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-24 15:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 13:55 [gentoo-user] which -march flag to pick for Intel Core 2 Duo in make.conf? Denis
2007-05-24 14:15 ` Ryan Sims
2007-05-24 14:17 ` Mark Shields
2007-05-24 15:13 ` Denis
2007-05-24 15:43 ` Neil Bothwick [this message]
2007-05-24 15:55 ` Graham Murray
2007-05-24 16:38 ` Denis
2007-05-25 7:22 ` Randy Barlow
2007-05-24 15:30 ` [gentoo-user] " Alexander Skwar
-- strict thread matches above, loose matches on Subject: below --
2007-05-25 9:10 [gentoo-user] " burlingk
2007-05-25 17:03 ` Andreas Claesson
2007-05-25 18:26 ` Denis
2007-05-28 3:05 ` Randy Barlow
2007-05-31 1:11 ` Dan Farrell
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=20070524164310.46a03922@zaphod.digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@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