All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Bryan Schumaker <bjschuma@netapp.com>
Cc: Billy Hass <billdh16@gmail.com>,
	Benny Halevy <bhalevy@tonian.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: Wed, 10 Aug 2011 11:29:07 -0700	[thread overview]
Message-ID: <4E42CDF3.6090708@panasas.com> (raw)
In-Reply-To: <4E42C9D3.2070006@netapp.com>

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 && mak=
e 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 =E2=80=98_xfs_vn_fallocate=E2=
=80=99:
>> fs/xfs/linux-2.6/xfs_iops.c:1070:3: error: implicit declaration of
>> function =E2=80=98xfs_setattr=E2=80=99 [-Werror=3Dimplicit-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
>=20
> This looks like an XFS problem now... did you see if any of the NFS c=
ode compiled this time?
>=20
> 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.
>=20
> - Bryan
>=20

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
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel=
" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Boaz Harrosh <bharrosh@panasas.com>
To: Bryan Schumaker <bjschuma@netapp.com>
Cc: Billy Hass <billdh16@gmail.com>,
	Benny Halevy <bhalevy@tonian.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: Wed, 10 Aug 2011 11:29:07 -0700	[thread overview]
Message-ID: <4E42CDF3.6090708@panasas.com> (raw)
In-Reply-To: <4E42C9D3.2070006@netapp.com>

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@vger.kernel.org>

Thanks
Boaz
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-08-10 18:29 UTC|newest]

Thread overview: 11+ 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 [this message]
2011-08-10 18:29               ` Boaz Harrosh
2011-08-10 19:05               ` Billy Hass
2011-08-10 19:05                 ` Billy Hass
     [not found]                 ` <CALPVbecSxKKbzo_CQqb075cZhiD5kOG7Aao71=cwktK1dSU2Zg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-08-11 12:17                   ` Benny Halevy
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=4E42CDF3.6090708@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=aglo@citi.umich.edu \
    --cc=bhalevy@tonian.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 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.