From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] kernel 4.9.77 error segfault in compile.
Date: Tue, 23 Jan 2018 12:30:51 -0500 [thread overview]
Message-ID: <CAGfcS_n-MXkqqaMuNS0p=yXML5wPrdgQydKu-djuRbHQuyt-hQ@mail.gmail.com> (raw)
In-Reply-To: <5e0e9718-5620-ba1a-3088-bc4b6ee60bd5@charter.net>
On Mon, Jan 22, 2018 at 9:34 PM, Corbin Bird <corbinbird@charter.net> wrote:
> On 01/22/2018 11:56 AM, Rich Freeman wrote:
>
> Tried both approaches ... the results :
>>
>> make distclean
>> make mrproper
>> --> copy over .config
>> make O=/var/tmp/linux modules_prepare
>> make O=/var/tmp/linux && make O=/var/tmp/linux modules_install
Two comments:
1. You don't need to run modules_prepare, unless you're just building
modules and not the rest of the kernel.
2. .config goes in /var/tmp/linux, not in /usr/src/linux.
It probably wouldn't hurt to wipe your sources and re-download them
instead of just running make mrproper (which won't fix modifications
made to source files). If you're using git sources you could just do
a hard git reset, which would fix any files in the repo.
I'll comment on your later reply...
--
Rich
next prev parent reply other threads:[~2018-01-23 17:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 15:51 [gentoo-user] kernel 4.9.77 error segfault in compile Corbin Bird
2018-01-22 17:11 ` Alexander Kapshuk
2018-01-22 17:56 ` Rich Freeman
2018-01-23 2:34 ` Corbin Bird
2018-01-23 7:42 ` Alexander Kapshuk
2018-01-23 8:03 ` Corbin Bird
2018-01-23 8:19 ` Alexander Kapshuk
2018-01-23 17:28 ` Corbin Bird
2018-01-23 17:35 ` Rich Freeman
2018-01-23 17:59 ` Wol's lists
2018-01-23 19:14 ` Corbin Bird
2018-01-24 1:55 ` Corbin Bird
2018-01-24 2:17 ` Rich Freeman
2018-01-23 17:30 ` Rich Freeman [this message]
2018-01-24 5:06 ` Adam Carter
2018-01-24 19:56 ` Corbin Bird
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='CAGfcS_n-MXkqqaMuNS0p=yXML5wPrdgQydKu-djuRbHQuyt-hQ@mail.gmail.com' \
--to=rich0@gentoo.org \
--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