From: Pavel Roskin <proski@gnu.org>
To: Andrey Semyonov <gatekeeper.mail@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: compat-wireless doesn't compile against 2.6.32 on Ubuntu beta
Date: Fri, 16 Apr 2010 17:50:10 -0400 [thread overview]
Message-ID: <1271454610.16507.33.camel@mj> (raw)
In-Reply-To: <t2wd01f95791004151011n1a5077a3oca9f7b641b311ac2@mail.gmail.com>
On Thu, 2010-04-15 at 21:11 +0400, Andrey Semyonov wrote:
> I get this when trying to compile current drivers:
>
>
> /usr/local/src/compat-wireless-2010-04-14# make
> make -C /lib/modules/2.6.32-19-generic/build
> M=/usr/local/src/compat-wireless-2010-04-14 modules
> make[1]: Вход в каталог `/usr/src/linux-headers-2.6.32-19-generic'
> CC [M] /usr/local/src/compat-wireless-2010-04-14/net/mac80211/main.o
> /usr/local/src/compat-wireless-2010-04-14/net/mac80211/main.c: In
> function 'ieee80211_alloc_hw':
> /usr/local/src/compat-wireless-2010-04-14/net/mac80211/main.c:394:
> error: implicit declaration of function '__hw_addr_init'
I confirm the problem. Basically, the bleeding edge compat-wireless is
useless now. Perhaps we need a check to to prevent broken tarballs from
being uploaded. It's better than force users to search for the last
working tarball.
compat-wireless-2.6.34-rc4 should be OK for Linux 2.6.27 and newer,
although it lacks some fixes needed for older kernels. It also lacks
the experimental wireless code that is not scheduled for Linux 2.6.34.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2010-04-16 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 17:11 compat-wireless doesn't compile against 2.6.32 on Ubuntu beta Andrey Semyonov
2010-04-16 21:50 ` Pavel Roskin [this message]
2010-04-16 23:29 ` Luis R. Rodriguez
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=1271454610.16507.33.camel@mj \
--to=proski@gnu.org \
--cc=gatekeeper.mail@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).