Mail archive

Re: [alpine-devel] Steps for adding / packaging a kernel module

From: Jeff Bilyk <>
Date: Sat, 7 Jan 2012 14:07:48 -0500

Hi Florian,

On Jan 7, 2012, at 4:34 AM, Florian Heigl <> wrote:

> Hi,
> i've been going through the wiki articles but so far this has been a
> quite inconclusive thing.

Agreed, it's another area where better docs would be appreciated.
> I've prepared a VM and installed alpine-sdk, and also somehow set up
> abuild, but I'm not even sure that was a step into the right
> direction.
> Ah, and just now I noticed the and stuff in aports.
> I want to try to build packages for flashcache and openvswitch at some
> point, right now I just want to install them "somehow" and test,
> that's why I end up needing to compile some kernel modules.
> Started a nice mass build of 1500 packages now and have no idea if
> that will really help me in the end :)
> Maybe this will just do it, but please take notice that one start-goal
> documentation for this would not hurt.

An example APKBUILD that you might check out would be Hopefully it can point you in the right direction. Before building packages with kernel modules you should only need to install alpine-sdk, any other source packages should be pulled in via the makedepends option.
> Greetings,
> Florian
> --
> the purpose of libvirt is to provide an abstraction layer hiding all
> xen features added since 2006 until they were finally understood and
> copied by the kvm devs.
> ---
> Unsubscribe:
> Help:
> ---

Received on Sat Jan 07 2012 - 14:07:48 UTC