From: Benny Halevy <bhalevy@tonian.com>
To: Billy Hass <billdh16@gmail.com>
Cc: Boaz Harrosh <bharrosh@panasas.com>,
Bryan Schumaker <bjschuma@netapp.com>,
Olga Kornievskaia <aglo@citi.umich.edu>,
linux-nfs@vger.kernel.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: Unable to Compile Latest Kernel from Git
Date: Thu, 11 Aug 2011 15:17:14 +0300 [thread overview]
Message-ID: <4E43C84A.1060402@tonian.com> (raw)
In-Reply-To: <CALPVbecSxKKbzo_CQqb075cZhiD5kOG7Aao71=cwktK1dSU2Zg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 2011-08-10 22:05, Billy Hass wrote:
> On Wed, Aug 10, 2011 at 2:29 PM, Boaz Harrosh <bharrosh@panasas.com> =
wrote:
>> On 08/10/2011 11:11 AM, Bryan Schumaker wrote:
>>> On 08/10/2011 01:29 PM, Billy Hass wrote:
>>>> [root@pdsi8 linux-pnfs]# make modules && make modules_install && m=
ake install
>>>> CHK include/linux/version.h
>>>> CHK include/generated/utsrelease.h
>>>> CALL scripts/checksyscalls.sh
>>>> CC [M] fs/xfs/linux-2.6/xfs_iops.o
>>>> fs/xfs/linux-2.6/xfs_iops.c: In function =91_xfs_vn_fallocate=92:
>>>> fs/xfs/linux-2.6/xfs_iops.c:1070:3: error: implicit declaration of
>>>> function =91xfs_setattr=92 [-Werror=3Dimplicit-function-declaratio=
n]
>>>> cc1: some warnings being treated as errors
>>>> make[2]: *** [fs/xfs/linux-2.6/xfs_iops.o] Error 1
>>>> make[1]: *** [fs/xfs] Error 2
>>>> make: *** [fs] Error 2
>>>
>>> This looks like an XFS problem now... did you see if any of the NFS=
code compiled this time?
>>>
>>> I've had these issues before, and it's usually caused by something =
in my .config. Generating a new one usually fixes it for me.
>>>
>>> - Bryan
>>>
>>
>> Please try v3.1-rc1 (git checkout v3.1-rc1) if it persists I'm sure =
the xfs guys
>> would like to fix it.
>>
>> Send this report with an attached .config file to:
>> linux-fsdevel <linux-fsdevel@vger.kernel.org>
>>
>> Thanks
>> Boaz
>>
>=20
> I tried v3.1-rc1 and it compiled successfully.
>=20
> Thanks for the help.
> --
The problem was a bad merge/rebase on my side.
Should be fixed now.
Thanks for reporting!
Benny
prev parent reply other threads:[~2011-08-11 12:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 1:58 Unable to Compile Latest Kernel from Git Billy Hass
[not found] ` <CALPVbefsY4Ddw6QOZu9BckCx+Q0YJg8tgbjK6xN5sQxbpdD16w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-08-08 19:01 ` Olga Kornievskaia
2011-08-09 8:52 ` Benny Halevy
2011-08-10 17:29 ` Billy Hass
[not found] ` <CALPVbedY4WV=Bsqr8Z0JUeYgrgVGLFc-NYdxJfewUAO0bJpR8A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-08-10 18:11 ` Bryan Schumaker
2011-08-10 18:29 ` Boaz Harrosh
2011-08-10 19:05 ` Billy Hass
[not found] ` <CALPVbecSxKKbzo_CQqb075cZhiD5kOG7Aao71=cwktK1dSU2Zg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-08-11 12:17 ` Benny Halevy [this message]
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=4E43C84A.1060402@tonian.com \
--to=bhalevy@tonian.com \
--cc=aglo@citi.umich.edu \
--cc=bharrosh@panasas.com \
--cc=billdh16@gmail.com \
--cc=bjschuma@netapp.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@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