From: james <garftd@verizon.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] march cflag for Intel Pentium Dual-Core E2160 SLA8Z Malay processor
Date: Tue, 18 Sep 2018 17:52:54 -0400 [thread overview]
Message-ID: <efbf47db-ca97-c545-740e-a2127915d423@verizon.net> (raw)
In-Reply-To: <CA+t6X7ev5G3ER4y7vcYThXupSvfhnUF3mwnMgsyTPAQPTneVow@mail.gmail.com>
On 9/18/18 3:22 AM, gevisz wrote:
> Currently, I am prepairing to build Gentoo system on
> computer with AMD Athlon 64 X2 for computer with
> Intel Pentium Dual-Core E2160 SLA8Z Malay processor.
>
> What will be the correct march cflag for Intel Pentium
> Dual-Core E2160 SLA8Z Malay processor to set up in
> make.conf ?
>
> Am I right to use amd64 stage3 for Intel Pentium
> Dual-Core E2160 SLA8Z Malay processor?
Once the system is 'boostrapped', you can run cpuinfo
and look at the flags listed therein. There are way less
gentoo flags one can set for a CPU, than what cpuinfo reveals.
Also some might not be a good idea to set; you have to ferret
out those details per your cpu(s).
hth,
James
next prev parent reply other threads:[~2018-09-18 21:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 7:22 [gentoo-user] march cflag for Intel Pentium Dual-Core E2160 SLA8Z Malay processor gevisz
2018-09-18 19:44 ` George Kettleborough
2018-09-19 21:45 ` gevisz
2018-09-19 21:54 ` Jack
2018-09-19 22:08 ` gevisz
2018-09-20 0:33 ` Andrew Udvare
2018-09-18 21:52 ` james [this message]
2018-09-19 21:52 ` gevisz
2018-09-19 8:37 ` Walter Dnes
2018-09-19 22:00 ` gevisz
2018-09-23 7:09 ` Walter Dnes
2018-09-24 15:49 ` james
2018-09-25 4:07 ` gevisz
2018-09-25 4:10 ` gevisz
2018-09-25 8:11 ` gevisz
2018-09-28 4:04 ` Walter Dnes
2018-09-28 9:33 ` Marc Joliet
2018-10-03 4:36 ` Mike Gilbert
2018-10-02 19:45 ` gevisz
2018-10-02 20:18 ` gevisz
2018-10-03 9:49 ` Walter Dnes
2018-10-03 11:03 ` gevisz
[not found] <wziCm-7RE-3@gated-at.bofh.it>
[not found] ` <wzGbE-4TG-5@gated-at.bofh.it>
[not found] ` <wzSPv-407-1@gated-at.bofh.it>
[not found] ` <wB6Qp-6uG-1@gated-at.bofh.it>
2018-09-24 15:30 ` james
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=efbf47db-ca97-c545-740e-a2127915d423@verizon.net \
--to=garftd@verizon.net \
--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