From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] systemtap support?
Date: Mon, 30 Aug 2010 18:29:55 +0200 [thread overview]
Message-ID: <20100830182955.42d397ea@surf> (raw)
In-Reply-To: <i5gkb0$72g$1@dough.gmane.org>
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
prev parent reply other threads:[~2010-08-30 16:29 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
2010-08-30 16:29 ` Thomas Petazzoni [this message]
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=20100830182955.42d397ea@surf \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox