[Buildroot] systemtap support?

[Buildroot] systemtap support?

[Grant Edwards]

I've figured out how to cross-compile a systemtap script ( generating
a kernel module for the target).  Now I need to build "staprun" for
the target.

Has anybody got a recipe for that?

I found a thread from a couple years ago indicating that somebody was
working on it, but haven't seen anything since:

  http://thread.gmane.org/gmane.comp.lib.uclibc.buildroot/9037

-- 
Grant Edwards               grant.b.edwards        Yow! if it GLISTENS,
                                  at               gobble it!!
                              gmail.com            

[Buildroot] systemtap support?

[Thomas Petazzoni]

Hello Grant,

On Fri, 27 Aug 2010 16:50:31 +0000 (UTC)
Grant Edwards <grant.b.edwards@gmail.com> wrote:

> I've figured out how to cross-compile a systemtap script ( generating
> a kernel module for the target).  Now I need to build "staprun" for
> the target.
> 
> Has anybody got a recipe for that?
> 
> I found a thread from a couple years ago indicating that somebody was
> working on it, but haven't seen anything since:
> 
>   http://thread.gmane.org/gmane.comp.lib.uclibc.buildroot/9037

I'm not aware of anything recent concerning the integration of
SystemTap into Buildroot. Feel free to work on this and submit your
patches!

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] systemtap support?

[Grant Edwards]

On 2010-08-27, Grant Edwards <grant.b.edwards@gmail.com> wrote:

> I've figured out how to cross-compile a systemtap script ( generating
> a kernel module for the target).  Now I need to build "staprun" for
> the target.

I've added a systemtap "AUTOTARGETS" package, but the configure is
failing because the configure script is trying to check for existence
of files.

AFAICT, the fix for that is to pass some environment variables to the
configure script that will short-circuit the file existence checks.

Something like this:

  ac_cv_file__usr_include_nspr=no \
  ac_cv_file__usr_include_nspr4=no \
  ac_cv_file__usr_include_nss=no \
  ac_cv_file__usr_include_nss3=no \
  ac_cv_func_malloc_0_nonnull=yes ./configure

How do you pass environment variables to the configure script when
using AUTOTARGETS?  

-- 
Grant Edwards               grant.b.edwards        Yow! I hope something GOOD
                                  at               came in the mail today so
                              gmail.com            I have a REASON to live!!

[Buildroot] systemtap support?

[Grant Edwards]

On 2010-08-30, Grant Edwards <grant.b.edwards@gmail.com> wrote:
> On 2010-08-27, Grant Edwards <grant.b.edwards@gmail.com> wrote:
>
>> I've figured out how to cross-compile a systemtap script ( generating
>> a kernel module for the target).  Now I need to build "staprun" for
>> the target.
>
> I've added a systemtap "AUTOTARGETS" package, but the configure is
> failing because the configure script is trying to check for existence
> of files.
>
> AFAICT, the fix for that is to pass some environment variables to the
> configure script that will short-circuit the file existence checks.
>
> Something like this:
>
>   ac_cv_file__usr_include_nspr=no \
>   ac_cv_file__usr_include_nspr4=no \
>   ac_cv_file__usr_include_nss=no \
>   ac_cv_file__usr_include_nss3=no \
>   ac_cv_func_malloc_0_nonnull=yes ./configure
>
> How do you pass environment variables to the configure script when
> using AUTOTARGETS?  

Never mind, I finally noticed xxxx_CONF_EVN in the documentation.

-- 
Grant Edwards               grant.b.edwards        Yow! I've read SEVEN
                                  at               MILLION books!!
                              gmail.com            

[Buildroot] systemtap support?

[Thomas Petazzoni]

On Mon, 30 Aug 2010 15:56:17 +0000 (UTC)
Grant Edwards <grant.b.edwards@gmail.com> wrote:

> >   ac_cv_file__usr_include_nspr=no \
> >   ac_cv_file__usr_include_nspr4=no \
> >   ac_cv_file__usr_include_nss=no \
> >   ac_cv_file__usr_include_nss3=no \
> >   ac_cv_func_malloc_0_nonnull=yes ./configure
> >
> > How do you pass environment variables to the configure script when
> > using AUTOTARGETS?  
> 
> Never mind, I finally noticed xxxx_CONF_EVN in the documentation.

Correct, <pkg>_CONF_ENV is the variable to use to pass such variables.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com