From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Strange compile errors
Date: Fri, 27 Apr 2018 18:43:27 +0100 [thread overview]
Message-ID: <4288024.bAQ0sQhltc@dell_xps> (raw)
In-Reply-To: <20180427172150.GC11753@ikki.ethgen.ch>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
On Friday, 27 April 2018 18:21:51 BST Klaus Ethgen wrote:
> Hi,
>
> Am Mi den 25. Apr 2018 um 18:56 schrieb Mick:
> > I recall there was a perl update recently. For good measure run:
> >
> > perl-cleaner --reallyall
> >
> > and then try running your remaining updates.
>
> That did the trick; even for the kernel. However, I had to compile the
> kernel with integrated firmware to skip this step in genkernel as
> genkernel failed with firmware compiling.
>
> Regards
> Klaus
I haven't used genkernel to be able to advise, but this page explains what you
need to do:
https://wiki.gentoo.org/wiki/Intel_microcode
However, you may find it makes no difference. Intel have announced they will
not be bringing out updated microcode to address the GPZ vulnerabilities for
any of their older CPUs. This has given me one more reason to never buy Intel
again.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-27 17:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 7:03 [gentoo-user] Kernel compile error Klaus Ethgen
2018-04-25 7:55 ` Christoph Böhmwalder
2018-04-25 8:15 ` Klaus Ethgen
2018-04-25 8:34 ` Alexander Kapshuk
2018-04-25 8:39 ` Christoph Böhmwalder
2018-04-25 11:51 ` Klaus Ethgen
2018-04-25 14:55 ` [gentoo-user] " Ian Zimmerman
2018-04-25 17:53 ` [gentoo-user] Strange compile errors Klaus Ethgen
2018-04-25 17:56 ` Mick
2018-04-27 17:21 ` Klaus Ethgen
2018-04-27 17:43 ` Mick [this message]
2018-04-27 18:01 ` Klaus Ethgen
2018-04-27 23:37 ` Peter Humphrey
2018-04-28 10:07 ` Mick
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=4288024.bAQ0sQhltc@dell_xps \
--to=michaelkintzios@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