From: Jeremy Wolcott <jeremy.wolcott@gmail.com>
To: tim.gardner@canonical.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: compat-wireless and DKMS
Date: Wed, 02 Sep 2009 13:11:06 -0400 [thread overview]
Message-ID: <4A9EA72A.3010504@gmail.com> (raw)
In-Reply-To: <4A9E9AEE.4060409@canonical.com>
Oh, cool. Is that in the Jaunty repositories? The latest kernel
release I'm seeing (with -proposed and -backports enabled) is 2.6.28-15...
Thanks,
-Jeremy
Tim Gardner wrote:
> Jeremy Wolcott wrote:
>> Has anybody tried to get compat-wireless working with DKMS? This
>> would be really handy for me since I run Ubuntu and they have been
>> pushing kernel updates pretty frequently lately, but I need the newest
>> compat-wireless to run my Atheros card in master mode via ath5k...
>>
>> I tried for quite a while today and the build just won't work. (The
>> 'make clean' step returns error 2, and then the build itself fails
>> with "(directory it's building in) is a directory. Stop.") I think
>> it's because the Makefile for compat-wireless uses the PWD environment
>> variable, but I'm not well-versed enough in Makefiles to fix it up so
>> that it'll work from a different directory (DKMS builds modules in
>> /var/lib/dkms/MODULE_NAME/VERSION/build instead of wherever I unpacked
>> the source).
>>
>> Any advice would be appreciated...
>>
>> Thanks,
>>
>> -Jeremy
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-wireless" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> I've been packaging compat-wireless in linux-backports-modules-2.6.31 on
> a semi-spasmodic basis. Current version contains wireless-testing
> master-2009-09-01.
>
> rtg
prev parent reply other threads:[~2009-09-02 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 14:22 compat-wireless and DKMS Jeremy Wolcott
2009-09-02 16:18 ` Tim Gardner
2009-09-02 17:11 ` Jeremy Wolcott [this message]
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=4A9EA72A.3010504@gmail.com \
--to=jeremy.wolcott@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=tim.gardner@canonical.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 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.