All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] systemtap support?
Date: Mon, 30 Aug 2010 15:56:17 +0000 (UTC)	[thread overview]
Message-ID: <i5gkb0$72g$1@dough.gmane.org> (raw)
In-Reply-To: i5gj7q$tev$1@dough.gmane.org

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            

  reply	other threads:[~2010-08-30 15:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-27 16:50 [Buildroot] systemtap support? Grant Edwards
2010-08-29  9:26 ` Thomas Petazzoni
2010-08-30 15:37 ` Grant Edwards
2010-08-30 15:56   ` Grant Edwards [this message]
2010-08-30 16:29     ` Thomas Petazzoni

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='i5gkb0$72g$1@dough.gmane.org' \
    --to=grant.b.edwards@gmail.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.