From: Nikos Chantziaras <realnc@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: CPU upgrade and LVM questions.
Date: Fri, 7 Dec 2018 08:22:41 +0200 [thread overview]
Message-ID: <pud3e4$eki$1@blaine.gmane.org> (raw)
In-Reply-To: <cc3d3018-71ee-bcdb-4144-d9f676b003a6@gmail.com>
On 07/12/2018 07:10, Dale wrote:
> Now this is odd. I changed the settings and ran emerge. I decided to
> use -UDNa options to see if it would catch the changes. It did. Thing
> is, outside a few video type packages, there were no packages to be
> rebuilt. It seems very few packages actually notice those settings.
That's correct. Some software has compile-time flags to enable/disable
specific CPU features. The ebuilds for that software use CPU_FLAGS_X86
to enable the relevant compile-time flags.
Most software doesn't contain low-level assembly code. Software that
does usually deals with video, audio or graphics, where hand crafted
low-level optimizations by the developers make sense.
If you want to see all of the installed packages that are affected, you
need to set CPU_FLAGS_X86 to an empty string:
CPU_FLAGS_X86=""
and then do "emerge -puDN --with-bdeps=y @world". This is because
CPU_FLAGS_X86 is not empty by default. It contains sse and sse2 by
default, because these are supported by all 64-bit CPUs.
> My only question left, will those flags affect the kernel image itself?
> I may just have to make sure my USB stick works.
No. The kernel configuration is completely separate from anything in
make.conf. CFLAGS or CPU_FLAGS_X86 do not affect kernel builds.
next prev parent reply other threads:[~2018-12-07 6:22 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 9:27 [gentoo-user] CPU upgrade and LVM questions Dale
2018-12-06 10:03 ` Neil Bothwick
2018-12-06 15:17 ` Dale
2018-12-06 16:51 ` J. Roeleveld
2018-12-06 18:36 ` Corbin Bird
2018-12-06 20:58 ` Dale
2018-12-06 21:24 ` Jack
2018-12-06 21:55 ` Dale
2018-12-07 1:06 ` Corbin Bird
2018-12-07 1:17 ` Dale
2018-12-07 5:10 ` Dale
2018-12-07 6:22 ` Nikos Chantziaras [this message]
2018-12-07 7:30 ` [gentoo-user] " Dale
2018-12-07 10:49 ` Alec Ten Harmsel
2018-12-07 23:47 ` Nikos Chantziaras
2018-12-07 23:59 ` Dale
2018-12-09 18:23 ` Taiidan
2018-12-09 18:57 ` J. Roeleveld
2018-12-09 22:41 ` Dale
2018-12-10 21:33 ` Taiidan
2018-12-10 22:14 ` Neil Bothwick
2018-12-10 22:54 ` Dale
2018-12-11 2:00 ` Taiidan
2018-12-11 8:49 ` Neil Bothwick
2018-12-11 9:23 ` Mick
2018-12-11 10:48 ` Dale
2018-12-11 15:14 ` J. Roeleveld
2018-12-11 22:46 ` Adam Carter
2018-12-11 23:56 ` Dale
2018-12-12 2:15 ` Adam Carter
2018-12-11 10:20 ` Alan Mackenzie
2018-12-11 15:03 ` J. Roeleveld
2018-12-07 8:47 ` [gentoo-user] " Neil Bothwick
2018-12-07 8:58 ` Dale
2018-12-06 21:02 ` [gentoo-user] " Nikos Chantziaras
2018-12-06 21:45 ` Dale
2018-12-06 22:22 ` Nikos Chantziaras
2018-12-06 23:23 ` Dale
2018-12-06 23:40 ` Nikos Chantziaras
2018-12-07 0:19 ` Dale
2018-12-07 10:01 ` Peter Humphrey
2018-12-07 12:41 ` Dale
2018-12-07 16:51 ` Peter Humphrey
2018-12-08 1:01 ` Dale
2018-12-08 2:51 ` Nikos Chantziaras
2018-12-08 4:39 ` Dale
2018-12-08 5:33 ` David Haller
2018-12-08 5:45 ` Dale
2018-12-08 6:00 ` Nikos Chantziaras
2018-12-08 6:28 ` David Haller
2018-12-08 4:23 ` David Haller
2018-12-08 5:35 ` Dale
2018-12-08 6:06 ` David Haller
2018-12-08 5:38 ` David Haller
2018-12-08 9:40 ` Peter Humphrey
2018-12-08 9:50 ` Peter Humphrey
2018-12-06 21:03 ` [gentoo-user] " Grant Taylor
2018-12-09 22:45 ` Dale
2018-12-10 1:35 ` Grant Taylor
2018-12-10 2:38 ` Dale
2018-12-10 3:37 ` Grant Taylor
2018-12-10 9:27 ` Neil Bothwick
2018-12-10 16:00 ` Dale
2018-12-08 17:49 ` Alexander Puchmayr
2018-12-08 18:23 ` Dale
2018-12-08 19:09 ` J. Roeleveld
2018-12-08 20:48 ` Dale
2018-12-11 10:41 ` Dale
2018-12-22 23:58 ` Dale
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='pud3e4$eki$1@blaine.gmane.org' \
--to=realnc@gmail.com \
--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