From: "John W. Linville" <linville@tuxdriver.com>
To: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: wireless-testing fail compiling
Date: Mon, 27 Feb 2012 18:29:47 -0500 [thread overview]
Message-ID: <20120227232946.GG26664@tuxdriver.com> (raw)
In-Reply-To: <1330374499.12612.18.camel@wwguy-huron>
On Mon, Feb 27, 2012 at 12:28:19PM -0800, Guy, Wey-Yi wrote:
> build break in the latest wireless-testing
>
> fs/autofs4/inode.c: In function ‘autofs4_fill_super’:
> fs/autofs4/inode.c:228: error: implicit declaration of function
> ‘is_compat_task’
> make[2]: *** [fs/autofs4/inode.o] Error 1
> make[1]: *** [fs/autofs4] Error 2
> make: *** [fs] Error 2
>
>
> fs/autofs4/dev-ioctl.c: In function ‘autofs_dev_ioctl_setpipefd’:
> fs/autofs4/dev-ioctl.c:388: error: implicit declaration of function
> ‘is_compat_task’
> make[2]: *** [fs/autofs4/dev-ioctl.o] Error 1
It looks like that line was added in commit
a32744d4abae24572eff7269bc17895c41bd0085, which came into
wireless-testing as part of 3.3-rc5.
FWIW, it built for me. I'm using a config derived from what is in
Fedora 17. Maybe you should try a clean build?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2012-02-27 23:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 20:28 wireless-testing fail compiling Guy, Wey-Yi
2012-02-27 23:29 ` John W. Linville [this message]
2012-02-29 7:51 ` Mohammed Shafi
2012-02-29 16:21 ` Randy Dunlap
2012-03-01 4:57 ` Mohammed Shafi
2012-03-01 15:19 ` John W. Linville
2012-03-01 15:51 ` Mohammed Shafi
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=20120227232946.GG26664@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wey-yi.w.guy@intel.com \
/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).