compiling a single kernel module package

View: New views
5 Messages — Rating Filter:   Alert me  

compiling a single kernel module package

by "Jens Möller" :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Hi @all!

I would like to modify a linux kernel module. Unfortunately, the module package has a postlinux.conf that does not seem to be executed when I start a compile for that single package. Recompiling the whole kernel is not much fun when developing a kernel module.

Is there a way to compile that single kernel module package?

Regards,

Jens
--
Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 -
sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser



-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
lists@... with a subject of: unsubscribe t2

Re: compiling a single kernel module package

by René Rebe :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

On 21.10.2009, at 13:11, Jens Möller wrote:


Hi @all!

I would like to modify a linux kernel module. Unfortunately, the module package has a postlinux.conf that does not seem to be executed when I start a compile for that single package. Recompiling the whole kernel is not much fun when developing a kernel module.

Is there a way to compile that single kernel module package?


In the past it was once possible to only build the third party modules by setting: SDEDEBUG_LINUX_SUBMODULES_ONLY, but due to changes in the kernel build system I think this does not work correctly anymore. But it's certainly fixable:

SDEDEBUG_LINUX_SUBMODULES_ONLY scripts/Build-Target -job 5-linux26 # etc. ...

However, you can also let the kernel build, and then enter the sandbox to continue developing / fixing where the build stopped in your module:

cd src.linuux26*
./debuig.sh

and then also include the sub-module defines, like:

. debug.buildenv.<name of module>

and continue building it with something like eval $MAKE $makeopt # etc. as appropriated for the module

Regards,
  René

-- 
  René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin


-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
lists@... with a subject of: unsubscribe t2

Re: compiling a single kernel module package

by netmana :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Rene,

That's exactly what i've been doing.  To enter the sandbox i added
hook in the premake in the file /target/<name>/pkg_linux26.conf, ie.

hook_add premake 5 "exit"

it works fine; however, i notice that when i try to add the same hook for
postmake, postflist or finish, the build process does not break.  Instead
it finishes building as usual.  I am not sure if that is normal.


Thank you.

Toan


On Thu, Oct 22, 2009 at 4:46 AM, Rene Rebe <rene@...> wrote:

> Hi,
> On 21.10.2009, at 13:11, Jens Möller wrote:
>
> Hi @all!
>
> I would like to modify a linux kernel module. Unfortunately, the module
> package has a postlinux.conf that does not seem to be executed when I start
> a compile for that single package. Recompiling the whole kernel is not much
> fun when developing a kernel module.
>
> Is there a way to compile that single kernel module package?
>
>
> In the past it was once possible to only build the third party modules by
> setting: SDEDEBUG_LINUX_SUBMODULES_ONLY, but due to changes in the kernel
> build system I think this does not work correctly anymore. But it's
> certainly fixable:
> SDEDEBUG_LINUX_SUBMODULES_ONLY scripts/Build-Target -job 5-linux26 # etc.
> ...
> However, you can also let the kernel build, and then enter the sandbox to
> continue developing / fixing where the build stopped in your module:
> cd src.linuux26*
> ./debuig.sh
> and then also include the sub-module defines, like:
> . debug.buildenv.<name of module>
> and continue building it with something like eval $MAKE $makeopt # etc. as
> appropriated for the module
> Regards,
>   René
> --
>   René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin
>   http://exactcode.com | http://t2-project.org | http://rene.rebe.name
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> lists@... with a subject of: unsubscribe t2
>
>

-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
lists@... with a subject of: unsubscribe t2

Re: compiling a single kernel module package

by René Rebe :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

It should break at all, but maybe exit is not enough, as it may not  
return a non-zero exit code. exit 1 might help. Better yet is just  
using the T2 function "abort":

hook_add postmake 5 abort

On 23.10.2009, at 06:50, Toan Pham wrote:

> Rene,
>
> That's exactly what i've been doing.  To enter the sandbox i added
> hook in the premake in the file /target/<name>/pkg_linux26.conf, ie.
>
> hook_add premake 5 "exit"
>
> it works fine; however, i notice that when i try to add the same  
> hook for
> postmake, postflist or finish, the build process does not break.  
> Instead
> it finishes building as usual.  I am not sure if that is normal.
>
>
> Thank you.
>
> Toan
>
>
> On Thu, Oct 22, 2009 at 4:46 AM, Rene Rebe <rene@...> wrote:
>> Hi,
>> On 21.10.2009, at 13:11, Jens Möller wrote:
>>
>> Hi @all!
>>
>> I would like to modify a linux kernel module. Unfortunately, the  
>> module
>> package has a postlinux.conf that does not seem to be executed when  
>> I start
>> a compile for that single package. Recompiling the whole kernel is  
>> not much
>> fun when developing a kernel module.
>>
>> Is there a way to compile that single kernel module package?
>>
>>
>> In the past it was once possible to only build the third party  
>> modules by
>> setting: SDEDEBUG_LINUX_SUBMODULES_ONLY, but due to changes in the  
>> kernel
>> build system I think this does not work correctly anymore. But it's
>> certainly fixable:
>> SDEDEBUG_LINUX_SUBMODULES_ONLY scripts/Build-Target -job 5-linux26  
>> # etc.
>> ...
>> However, you can also let the kernel build, and then enter the  
>> sandbox to
>> continue developing / fixing where the build stopped in your module:
>> cd src.linuux26*
>> ./debuig.sh
>> and then also include the sub-module defines, like:
>> . debug.buildenv.<name of module>
>> and continue building it with something like eval $MAKE $makeopt #  
>> etc. as
>> appropriated for the module
>> Regards,
>>   René
>> --
>>   René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin
>>   http://exactcode.com | http://t2-project.org | http://
>> rene.rebe.name
>>
>> -----------------------------------------------------------
>> If you wish to unsubscribe from this mailing, send mail to
>> lists@... with a subject of: unsubscribe t2
>>
>>
--
   René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin
   http://exactcode.com | http://t2-project.org | http://rene.rebe.name


-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
lists@... with a subject of: unsubscribe t2

Re: compiling a single kernel module package

by "Jens Möller" :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Hi.

Thanks for your help. I used

hook_add premake 5 abort

to get a working copy of the kernels directory. After that I can reconfigure the environment as you showed and compile my kernel module.

CU,

Jens


-------- Original-Nachricht --------
> Datum: Fri, 23 Oct 2009 09:48:59 +0200
> Von: Rene Rebe <rene@...>
> An: Toan Pham <tpham3783@...>
> CC: "Jens Möller" <komischername@...>, T2 developers mailing list <t2@...>
> Betreff: Re: [t2] compiling a single kernel module package

> It should break at all, but maybe exit is not enough, as it may not  
> return a non-zero exit code. exit 1 might help. Better yet is just  
> using the T2 function "abort":
>
> hook_add postmake 5 abort
>
> On 23.10.2009, at 06:50, Toan Pham wrote:
>
> > Rene,
> >
> > That's exactly what i've been doing.  To enter the sandbox i added
> > hook in the premake in the file /target/<name>/pkg_linux26.conf, ie.
> >
> > hook_add premake 5 "exit"
> >
> > it works fine; however, i notice that when i try to add the same  
> > hook for
> > postmake, postflist or finish, the build process does not break.  
> > Instead
> > it finishes building as usual.  I am not sure if that is normal.
> >
> >
> > Thank you.
> >
> > Toan
> >
> >
> > On Thu, Oct 22, 2009 at 4:46 AM, Rene Rebe <rene@...> wrote:
> >> Hi,
> >> On 21.10.2009, at 13:11, Jens Möller wrote:
> >>
> >> Hi @all!
> >>
> >> I would like to modify a linux kernel module. Unfortunately, the  
> >> module
> >> package has a postlinux.conf that does not seem to be executed when  
> >> I start
> >> a compile for that single package. Recompiling the whole kernel is  
> >> not much
> >> fun when developing a kernel module.
> >>
> >> Is there a way to compile that single kernel module package?
> >>
> >>
> >> In the past it was once possible to only build the third party  
> >> modules by
> >> setting: SDEDEBUG_LINUX_SUBMODULES_ONLY, but due to changes in the  
> >> kernel
> >> build system I think this does not work correctly anymore. But it's
> >> certainly fixable:
> >> SDEDEBUG_LINUX_SUBMODULES_ONLY scripts/Build-Target -job 5-linux26  
> >> # etc.
> >> ...
> >> However, you can also let the kernel build, and then enter the  
> >> sandbox to
> >> continue developing / fixing where the build stopped in your module:
> >> cd src.linuux26*
> >> ./debuig.sh
> >> and then also include the sub-module defines, like:
> >> . debug.buildenv.<name of module>
> >> and continue building it with something like eval $MAKE $makeopt #  
> >> etc. as
> >> appropriated for the module
> >> Regards,
> >>   René
> >> --
> >>   René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin
> >>   http://exactcode.com | http://t2-project.org | http://
> >> rene.rebe.name
> >>
> >> -----------------------------------------------------------
> >> If you wish to unsubscribe from this mailing, send mail to
> >> lists@... with a subject of: unsubscribe t2
> >>
> >>
>
> --
>    René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin
>    http://exactcode.com | http://t2-project.org | http://rene.rebe.name

--
Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 -
sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser



-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
lists@... with a subject of: unsubscribe t2