From: Andrew Morton <akpm@linux-foundation.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Joe Perches <joe@perches.com>,
Adam Borowski <kilobyte@angband.pl>,
Michal Marek <mmarek@suse.com>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
ben@decadent.org.uk, Sven Joachim <svenjoac@gmx.de>
Subject: Re: [RFC PATCH] kbuild: add -fno-PIE
Date: Fri, 28 Oct 2016 16:00:17 -0700 [thread overview]
Message-ID: <20161028160017.ebcb3a97f8e225f5f20fd874@linux-foundation.org> (raw)
In-Reply-To: <20161027072824.rt3d6wngz7lrfb7u@linutronix.de>
On Thu, 27 Oct 2016 09:28:24 +0200 Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
> > Building with gcc 3.3 is apparently still possible, although it produces
> > tons of warnings and a modpost section mismatch. Still, requiring gcc
> > 4.1 or newer would not be unreasonable, I think (still released a few
> > months earlier than binutils 2.17).
>
> I remember you had once a server box running some enterprise distro
> which had an old gcc. Do you see any reason for not lifting the minimum
> gcc version to v4.1 ?
Seems OK to me. I do have a gcc-3.4.5 for mips, sh and sparc64 sitting
around but I basically never use them and should update.
next prev parent reply other threads:[~2016-10-28 23:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 11:16 Sebastian Andrzej Siewior
2016-10-21 21:21 ` Adam Borowski
2016-10-23 16:19 ` Sven Joachim
2016-10-23 19:23 ` Joe Perches
2016-10-24 7:38 ` Sven Joachim
2016-10-24 7:43 ` Sebastian Andrzej Siewior
2016-10-24 17:32 ` Sven Joachim
2016-10-24 17:48 ` Joe Perches
2016-10-25 7:30 ` Sebastian Andrzej Siewior
2016-10-26 17:51 ` Sven Joachim
2016-10-27 7:28 ` Sebastian Andrzej Siewior
2016-10-28 23:00 ` Andrew Morton [this message]
2016-10-29 10:10 ` Tomas Janousek
2016-10-29 17:03 ` Sven Joachim
2016-10-29 19:21 ` Tomas Janousek
2016-10-29 21:18 ` Sven Joachim
2016-10-24 9:57 ` Joe Perches
2016-10-27 17:09 ` Shuah Khan
2016-10-28 8:09 ` Sebastian Andrzej Siewior
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=20161028160017.ebcb3a97f8e225f5f20fd874@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ben@decadent.org.uk \
--cc=bigeasy@linutronix.de \
--cc=joe@perches.com \
--cc=kilobyte@angband.pl \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=svenjoac@gmx.de \
/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
Powered by JetHome