From: Billy Hass <billdh16-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Boaz Harrosh <bharrosh-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
Cc: Bryan Schumaker
<bjschuma-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>,
Benny Halevy <bhalevy-4/WYdZTkCtzQT0dZR+AlfA@public.gmane.org>,
Olga Kornievskaia <aglo-vtMw8L3fJ9vSiEDVxGk4TQ@public.gmane.org>,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-fsdevel
<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Unable to Compile Latest Kernel from Git
Date: Wed, 10 Aug 2011 15:05:02 -0400 [thread overview]
Message-ID: <CALPVbecSxKKbzo_CQqb075cZhiD5kOG7Aao71=cwktK1dSU2Zg@mail.gmail.com> (raw)
In-Reply-To: <4E42CDF3.6090708-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
On Wed, Aug 10, 2011 at 2:29 PM, Boaz Harrosh <bharrosh-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org> 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 && make 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 ‘_xfs_vn_fallocate’:
>>> fs/xfs/linux-2.6/xfs_iops.c:1070:3: error: implicit declaration of
>>> function ‘xfs_setattr’ [-Werror=implicit-function-declaration]
>>> 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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
>
> Thanks
> Boaz
>
I tried v3.1-rc1 and it compiled successfully.
Thanks for the help.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-08-10 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALPVbefsY4Ddw6QOZu9BckCx+Q0YJg8tgbjK6xN5sQxbpdD16w@mail.gmail.com>
[not found] ` <CAN-5tyEmCx+1quj+545zDZ1ueQRVhHGgDzhdjZ1K1h6hCjOJvw@mail.gmail.com>
[not found] ` <4E40F53A.2080303@tonian.com>
[not found] ` <CALPVbedY4WV=Bsqr8Z0JUeYgrgVGLFc-NYdxJfewUAO0bJpR8A@mail.gmail.com>
[not found] ` <4E42C9D3.2070006@netapp.com>
2011-08-10 18:29 ` Unable to Compile Latest Kernel from Git Boaz Harrosh
[not found] ` <4E42CDF3.6090708-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
2011-08-10 19:05 ` Billy Hass [this message]
[not found] ` <CALPVbecSxKKbzo_CQqb075cZhiD5kOG7Aao71=cwktK1dSU2Zg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-08-11 12:17 ` Benny Halevy
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='CALPVbecSxKKbzo_CQqb075cZhiD5kOG7Aao71=cwktK1dSU2Zg@mail.gmail.com' \
--to=billdh16-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=aglo-vtMw8L3fJ9vSiEDVxGk4TQ@public.gmane.org \
--cc=bhalevy-4/WYdZTkCtzQT0dZR+AlfA@public.gmane.org \
--cc=bharrosh-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org \
--cc=bjschuma-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).