From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: Hin-Tak Leung <hintak.leung@gmail.com>
Cc: Linux Wireless List <linux-wireless@vger.kernel.org>
Subject: Re: Some remarks about compat-wireless KBuild system
Date: Thu, 14 Jan 2010 19:04:49 +0200 [thread overview]
Message-ID: <4B4F4EB1.7020300@pardus.org.tr> (raw)
In-Reply-To: <3ace41891001131903g38f4da27w6f469e6121eaf668@mail.gmail.com>
Hin-Tak Leung wrote:
> On Wed, Jan 13, 2010 at 5:02 PM, Ozan Çağlayan <ozan@pardus.org.tr> wrote:
>> Hi,
>>
>> Current compat-wireless build system has some inconveniences for distribution packaging:
>>
>>
>> - In Makefile, KLIB is set to /lib/modules/$(uname -r) which avoids compiling the stack
>> against a non-running kernel. In several other external kernel drivers this can be bypassed
>> by giving KERNELRELEASE=something to "make" but it's not working for compat-wireless.
>
> Did you not read README (or the instruction in the README not working
> any more)?
>
> compat-wireless can be used with a non-running kernel, and the
> instruction is in the top-level README. (I contributed part of it, the
> part on the non-running kernel which has just been distro-installed,
> e.g. to build and install compat-wireless during a routine upgrade
> which installs a new kernel but before a reboot to it).
Hi,
actually yes I've read it many times to not miss anything about packaging but I didn't see that part.
The instructions are still correct and building against a non-running kernel and installing to a different
directory works without problem.
sorry for the inconvenience, thanks!
Ozan Caglayan
prev parent reply other threads:[~2010-01-14 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 17:02 Some remarks about compat-wireless KBuild system Ozan Çağlayan
2010-01-14 3:03 ` Hin-Tak Leung
2010-01-14 17:04 ` Ozan Çağlayan [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=4B4F4EB1.7020300@pardus.org.tr \
--to=ozan@pardus.org.tr \
--cc=hintak.leung@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 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.