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: Sat, 28 Jun 2014 11:55:07 +0100 [thread overview]
Message-ID: <53AE9F0B.1080207@linicks.net> (raw)
In-Reply-To: <53AE9863.6050102@linicks.net>
On 28/06/14 11:26, Nick Warne wrote:
>
> On 28/06/14 11:12, Borislav Petkov wrote:
>> On Sat, Jun 28, 2014 at 10:52:24AM +0100, Nick Warne wrote:
>>> Hi Everybody,
>>>
>>> Today I was trying to build 3.15.2 on AMD64 from kernel 3.14.8 and get this:
>>>
>>> CC fs/mbcache.o
>>> fs/mbcache.c: In function ‘__spin_lock_mb_cache_entry’:
>>> fs/mbcache.c:134: error: SSE register return with SSE disabled
>>> make[1]: *** [fs/mbcache.o] Error 1
>>
>> I can't trigger that here.
>>
>> Please send your .config. Also, before building, did you clean up your
>> source tree properly by saving the .config somewhere else and doing
>> "make mrproper"?
>
> Thanks for prompt reply.
>
> I always do a mrproper followed by grabbing current .config from /proc
> and issuing make oldconfig.
>
> Attached is my config file.
>
> Also, for what it is worth:
>
> gcc version 4.8.2 (GCC)
Whoops - that is WRONG (too many ssh terminals)
gcc version 4.2.4
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-28 10:55 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 [this message]
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
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=53AE9F0B.1080207@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox