Re: [alpine-devel] Steps for adding / packaging a kernel module
On Jan 7, 2012, at 4:34 AM, Florian Heigl <florian.heigl_at_gmail.com> wrote:
> 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
> Ah, and just now I noticed the rebuild-alpine.sh 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 http://git.alpinelinux.org/cgit/aports/tree/main/open-vm-tools-grsec/APKBUILD
. 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.
> 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: alpine-devel+unsubscribe_at_lists.alpinelinux.org
> Help: alpine-devel+help_at_lists.alpinelinux.org
Received on Sat Jan 07 2012 - 14:07:48 UTC