From: Nick Warne <nick@linicks.net>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3.15.2 build error on AMD64
Date: Mon, 30 Jun 2014 19:51:00 +0100 [thread overview]
Message-ID: <53B1B194.3060907@linicks.net> (raw)
In-Reply-To: <20140630132637.GD4766@pd.tnic>
On 30/06/14 14:26, Borislav Petkov wrote:
> On Sun, Jun 29, 2014 at 11:24:23PM +0200, Borislav Petkov wrote:
>> Btw, I thought you had that gcc 4.2.x from some distro or so. Because
>> if it is in some ancient distro, one could install it in kvm and test
>> and play with it.
>
> Ok, I did dig out an ancient debian I had lying around here with gcc
> 4.1.2. The patch I pointed you at does really fix the issue. So all is
> fine and solved now. :-)
Ummm, interesting.
But is it solved?
Suppose developer a.n.other submits a patch that works with his/her GCC
version but doesn't with some other GCC version. I guess this will be
picked up in GIT build tests, but that only then tells everybody to
upgrade GCC or find a patch that fixes the issue (like you did, but I
couldn't find it).
Is there a document or something that stipulates what is the minimum
version[s] of GCC to build a particular version of the kernel? If not,
perhaps this is something that needs addressing.
Nick
--
"A bug in the code is worth two in the documentation."
FSF Associate Member 5508
http://linicks.net/
http://pi.linicks.net/
next prev parent reply other threads:[~2014-06-30 18:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-28 9:52 3.15.2 build error on AMD64 Nick Warne
2014-06-28 10:12 ` Borislav Petkov
2014-06-28 10:26 ` Nick Warne
2014-06-28 10:55 ` Nick Warne
2014-06-28 12:23 ` Borislav Petkov
2014-06-28 13:09 ` Nick Warne
2014-06-29 19:06 ` Nick Warne
2014-06-29 19:44 ` Borislav Petkov
2014-06-29 21:05 ` Nick Warne
2014-06-29 21:24 ` Borislav Petkov
2014-06-30 13:26 ` Borislav Petkov
2014-06-30 18:51 ` Nick Warne [this message]
2014-06-30 19:23 ` Borislav Petkov
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=53B1B194.3060907@linicks.net \
--to=nick@linicks.net \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.