From: Borislav Petkov <bp@alien8.de>
To: Nick Warne <nick@linicks.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3.15.2 build error on AMD64
Date: Sat, 28 Jun 2014 14:23:22 +0200 [thread overview]
Message-ID: <20140628122322.GC4373@pd.tnic> (raw)
In-Reply-To: <53AE9F0B.1080207@linicks.net>
On Sat, Jun 28, 2014 at 11:55:07AM +0100, Nick Warne wrote:
> Whoops - that is WRONG (too many ssh terminals)
>
> gcc version 4.2.4
That's some old compiler. Anyway, I can't trigger it here with gcc 4.6
and 4.9.
Can you do
$ make clean
$ make V=1 fs/mbcache.i >>w.log 2>&1
$ make V=1 fs/mbcache.s >>w.log 2>&1
and zip and send me fs/mbcache.i, fs/mbcache.s and w.log.
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-06-28 12:23 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 [this message]
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
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=20140628122322.GC4373@pd.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.net \
/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