From: Peter Johanson <latexer@gentoo.org>
To: Daniel Drake <dsd@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] FYI: koutput/config-kernel should *NOT* be used/supported currently.
Date: Sat, 2 Oct 2004 07:09:22 -0700 [thread overview]
Message-ID: <20041002140921.GC15672@butchy.cubesearch.com> (raw)
In-Reply-To: <415EBDEA.1030804@gentoo.org>
On Sat, Oct 02, 2004 at 03:40:42PM +0100, Daniel Drake wrote:
> Hi Peter,
>
> Peter Johanson wrote:
> >Hey all,
> >As a result, the kmod.eclass, and config-kernel have several problems,
> >and are only 1/2 implemented anyway. Sooo, don't use kmod.eclass. Just
> >don't. config-kernel i will be package.masking as well soon.
>
> In that case, how should ebuilds go about building/installing external 2.6
> modules for now? Any "model" ebuilds you can point me at?
As of 2.6.6, a new parameter "M=" was added, to take the place of using
SUBDIRS= when invoking the kernel build system outside of the kernel.
This, combined with some other kernel build fixes, meant that the kernel
build system wouldn't have to write to things all over the
/usr/src/linux tree when compiling external modules.
Most of the time, this means a simple sed to do s:SUBDIRS=:M=: on a
makefile or two is sufficient. This doesn't account for any older
kernels, but at this point, older 2.6 kernels have quite a few security
vulnerabilities ,and should be upgraded anyway.
For example ebuilds, check out the new hostap-driver or ipw2100 ebuilds,
that do the above technique. Feel free to email me in private or catch
me on IRC if you want help with any particular ebuilds.
-pete
>
> Thanks,
>
> Daniel
>
--
Peter Johanson
<latexer@gentoo.org>
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2004-10-02 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 2:26 [gentoo-dev] FYI: koutput/config-kernel should *NOT* be used/supported currently Peter Johanson
2004-10-02 14:40 ` Daniel Drake
2004-10-02 14:09 ` Peter Johanson [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=20041002140921.GC15672@butchy.cubesearch.com \
--to=latexer@gentoo.org \
--cc=dsd@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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