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: Mon, 22 Jan 2018 12:56:30 -0500 [thread overview]
Message-ID: <CAGfcS_ntiRyuq+tXdBCRw2qGN92oY4rfRRSUVd=ULpcJ5QfpvQ@mail.gmail.com> (raw)
In-Reply-To: <CAJ1xhMXHpLM4jULa8HqfPvaeumvZZGiQUMtEw8Tg8SNLaXK+nQ@mail.gmail.com>
On Mon, Jan 22, 2018 at 12:11 PM, Alexander Kapshuk
<alexander.kapshuk@gmail.com> wrote:
> On Mon, Jan 22, 2018 at 5:51 PM, Corbin Bird <corbinbird@charter.net> wrote:
>> Anyone else getting this error? ( kernel 4.9.77 )
>>
>>> CC fs/ext4/mballoc.o
>>> CC fs/ext4/block_validity.o
>>> CC fs/ext4/move_extent.o
>>> CC fs/ext4/mmp.o
>>> CC fs/ext4/indirect.o
>>> fs/ext4/indirect.o: warning: objtool: ext4_clear_blocks()+0x242: can't
>>> find jump dest instruction at .text+0x56c
>>> CC fs/ext4/extents_status.o
>>> /bin/sh: line 1: 31735 Segmentation fault ./tools/objtool/objtool
>>> check "fs/ext4/extents_status.o"
>>> make[2]: *** [scripts/Makefile.build:294: fs/ext4/extents_status.o]
>>> Error 139
>>> make[1]: *** [scripts/Makefile.build:544: fs/ext4] Error 2
>>> make: *** [Makefile:995: fs] Error 2
>>
>> Corbin
>>
>>
>
> Based on the output you supplied, objtool isn't happy with
> fs/ext4/indirect.o and fs/ext4/extents_status.o.
> Did you do 'make clean' prior to building the kernel?
> If you did, it might be worth doing a 'make mrproper' before
> rebuilding the kernel.
> Don't forget to back up your .config before running mrproper.
>
While this is going to cause a bit more building, I personally tend to
redirect kernel build output. I add O=/var/tmp/linux to all my make
commands, which leaves /usr/src untouched and builds faster besides
(tmpfs).
The main downsides to this are:
1. Make can't re-use objects from previous builds, so rebuilds will
go slower. Though, IMO this is worthwhile if re-using those objects
causes issues (which I assume is due to imperfect makefiles).
2. When building packages that install kernel modules the prepared
sources won't exist. This requires going back and re-preparing them
(make O=/var/tmp/linux modules_prepare). For packages like zfs-kmod
that use Module.symvers this is even more painful as you can only get
that by rebuilding the whole thing.
--
Rich
next prev parent reply other threads:[~2018-01-22 17:56 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 [this message]
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
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_ntiRyuq+tXdBCRw2qGN92oY4rfRRSUVd=ULpcJ5QfpvQ@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