From: "Stefan G. Weichinger" <lists@xunil.at>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Rebuilding a kernel on a hardened gentoo
Date: Tue, 11 Sep 2018 12:39:54 +0200 [thread overview]
Message-ID: <a22dabe8-4c11-b58d-e420-f8a213041218@xunil.at> (raw)
In-Reply-To: <8ca0a958-6604-d4b7-3555-4cd7daf92fbd@xunil.at>
Am 11.09.18 um 11:48 schrieb Stefan G. Weichinger:
> Right now I always get this when I run "make bzImage" (
>
> # make bzImage
> CHK include/config/kernel.release
> CHK include/generated/uapi/linux/version.h
> CHK include/generated/utsrelease.h
> CC kernel/bounds.s
> kernel/bounds.c:1:0: error: code model kernel does not support PIC mode
> /*
>
> make[1]: *** [Kbuild:44: kernel/bounds.s] Error 1
> make: *** [Makefile:990: prepare0] Error 2
>
> Why?
> Because the gcc has flags enabled?
>
> I googled but klibc-related stuff doesn't seem to apply here.
>
> I am not insisting on hardened profile but want to avoid bigger issues
> when switching profiles without thinking ...
I managed to compile a 4.9.95 after "make localmodconfig". Maybe that
would help with the other kernels as well.
next prev parent reply other threads:[~2018-09-11 10:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 9:48 [gentoo-user] Rebuilding a kernel on a hardened gentoo Stefan G. Weichinger
2018-09-11 10:39 ` Stefan G. Weichinger [this message]
2018-09-11 10:54 ` Mick
2018-09-12 7:59 ` Stefan G. Weichinger
2018-09-12 9:41 ` Adam Carter
2018-09-12 6:42 ` J. Roeleveld
2018-09-12 7:43 ` Stefan G. Weichinger
2018-09-12 8:09 ` Stefan G. Weichinger
2018-09-12 8:15 ` Stefan G. Weichinger
2018-11-07 9:42 ` Stefan G. Weichinger
2018-11-07 9:45 ` Stefan G. Weichinger
2018-11-09 7:02 ` Stefan G. Weichinger
2018-09-12 12:14 ` J. Roeleveld
2018-09-12 13:07 ` J. Roeleveld
2018-09-14 6:34 ` Stefan G. Weichinger
2018-09-14 8:15 ` J. Roeleveld
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=a22dabe8-4c11-b58d-e420-f8a213041218@xunil.at \
--to=lists@xunil.at \
--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