From: Randy Dunlap <rdunlap@xenotime.net>
To: Ouyang <ilhebe999@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: make moduels tx.c error
Date: Sun, 17 Jun 2012 23:05:59 -0700 [thread overview]
Message-ID: <4FDEC547.1080701@xenotime.net> (raw)
In-Reply-To: <loom.20120617T234255-222@post.gmane.org>
On 06/17/2012 02:45 PM, Ouyang wrote:
> Anyone can tell me how to figure this problem? I do not have much experience on
> linux kernel compiling.
> make modules
> make[1]: Nothing to be done for `all'.
> CHK include/linux/version.h
> CHK include/generated/utsrelease.h
> CALL scripts/checksyscalls.sh
> CC [M] net/mac80211/tx.o
> net/mac80211/tx.c: In function ‘ieee80211_tx’:
> net/mac80211/tx.c:1327:2: error: implicit declaration of function
> ‘ieee80211_tx_prepare’ [-W
> net/mac80211/tx.c: At top level:
> net/mac80211/tx.c:1601:1: error: conflicting types for ‘ieee80211_tx_prepare’
> net/mac80211/tx.c:1327:16: note: previous implicit declaration of
> ‘ieee80211_tx_prepare’ was
> net/mac80211/tx.c: In function ‘ieee80211_tx_prepare’:
> net/mac80211/tx.c:1643:7: warning: passing argument 1 of
> ‘__ieee80211_parse_tx_radiotap’ fro
> net/mac80211/tx.c:1516:13: note: expected ‘struct sk_buff *’ but argument is of
> type ‘struct
> net/mac80211/tx.c:1643:7: error: too many arguments to function
> ‘__ieee80211_parse_tx_radiot
> net/mac80211/tx.c:1516:13: note: declared here
> net/mac80211/tx.c: In function ‘ieee80211_monitor_start_xmit’:
> net/mac80211/tx.c:1790:2: error: implicit declaration of function
> ‘ieee80211_parse_tx_radiot
> cc1: some warnings being treated as errors
> make[2]: *** [net/mac80211/tx.o] Error 1
> make[1]: *** [net/mac80211] Error 2
> make: *** [net] Error 2
What kernel version is this?
What commands did you use to do the build?
thanks,
--
~Randy
next prev parent reply other threads:[~2012-06-18 6:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 21:45 make moduels tx.c error Ouyang
2012-06-18 6:05 ` Randy Dunlap [this message]
2012-06-18 18:03 ` Ouyang
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=4FDEC547.1080701@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=ilhebe999@gmail.com \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).