From: "Gerrit Kühn" <gerrit.kuehn@aei.mpg.de>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] kernel 3.2 conflicts with gcc-6.4
Date: Fri, 9 Feb 2018 08:01:53 +0100 [thread overview]
Message-ID: <20180209080153.b1bde412b81290c9dc9e6bad@aei.mpg.de> (raw)
Hello,
I still have some systems around that need to run a vanilla kernel 3.2.
This works without any issues as long as I am using gcc-4.9.4 or gcc-5.4 to
compile the kernel. Using gcc-6.4 for compilation was not possible
out-of-the-box as it is defaulting to --enable-default-pie.
After reading https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841420 I
was able to get around this by adding -fno-pie to the build. However, when
trying to run this kernel, it does not output anything and just reboots my
system. Compiling the same source and setup (even including my additional
-fno-pie settings) with gcc-5.4 or gcc-4.9.4 results in a kernel that is
running fine, just with gcc-6.4 it appears to be broken.
Is there anyone around who successfully managed to get this to work (or
who has any other hints how to fix this)?
Now that Gentoo has deprecated 2013's profile, using gcc4 or gcc5 is not
really supported for anything, and I'd like to avoid having to compile
different parts of the system with different compilers.
cu
Gerrit
reply other threads:[~2018-02-09 7:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180209080153.b1bde412b81290c9dc9e6bad@aei.mpg.de \
--to=gerrit.kuehn@aei.mpg.de \
--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