From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Natanael Copa <natanael.copa@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: building compat-wireless for other than running kernels
Date: Wed, 2 Sep 2009 14:25:10 -0700 [thread overview]
Message-ID: <43e72e890909021425s13784658r342e52eefb7b582d@mail.gmail.com> (raw)
In-Reply-To: <95408c820909021353i5b2d0e5dpeddefcdb5065d724@mail.gmail.com>
On Wed, Sep 2, 2009 at 1:53 PM, Natanael Copa<natanael.copa@gmail.com> wrote:
> Hi,
> I'm trying to create a compat-wireless package for Alpine Linux. I get
> errors like this:
> FATAL: Could not load
> /lib/modules/2.6.29.4-vs2.3.0.36.14-ARCH/modules.dep: No such file or
> directory
> This comes from the fact that the package is not for the current running kernel.
>
> It would be nice if modprobe and depmod could respect the KLIB
> variable in makefile. (I have not figured out how to do that for
> modprobe -l)
>
> Alternatively you could define a DEPMOD=/sbin/depmod in the Makefile
> so its possible to override it with: make DEPMOD=: ...
Patches are welcomed. I considered just now added the depmod stuff you
mentioned but remembered that there are also scripts which may use
this on compat-wireless. We could just export it though and then all
the scripts would have access to it -- but note that it means then
that you'd need the Makefile to run certain scripts -- and if you
don't you have to define your own depmod. Because of this I welcome
your patches on this if you test it.
Luis
next prev parent reply other threads:[~2009-09-02 21:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 20:53 building compat-wireless for other than running kernels Natanael Copa
2009-09-02 21:25 ` Luis R. Rodriguez [this message]
2009-09-02 22:00 ` Natanael Copa
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=43e72e890909021425s13784658r342e52eefb7b582d@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=natanael.copa@gmail.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