From: Patrick Doyle <wpdster@gmail.com>
To: "Allen Kennedy Jr." <allen@kennedystuff.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Environment Variables being unset by bitbake?
Date: Wed, 9 Jul 2014 19:11:15 -0400 [thread overview]
Message-ID: <CAF_dkJA_5nbzfAA02_CCxmEZ3vJjjQXYXqFRhV_HsmyuuuPuiA@mail.gmail.com> (raw)
In-Reply-To: <CAO-21LPnS-BJyZw-SEiSveK5sP=sZaDnMRd9PHVVe5WG6NQG_A@mail.gmail.com>
Oh! I think I know the answer to this one!
Check out BB_ENV_EXTRAWHITE at
http://www.yoctoproject.org/docs/current/bitbake-user-manual/bitbake-user-manual.html#var-BB_ENV_EXTRAWHITE.
If you set that to something like JAVA_HOME, that might do what you
want.
--wpd
On Wed, Jul 9, 2014 at 4:58 PM, Allen Kennedy Jr.
<allen@kennedystuff.com> wrote:
> I am trying to run java program from a recipe.
>
> I get an error that JAVA_HOME is not set.
> I can verify that JAVA_HOME is set by echo $JAVA_HOME.
>
> I can then run the program without issue, but from within a recipe it
> seems that $JAVA_HOME is unset.
>
> I have verified this with 'bbnote "java is here: ${JAVA_HOME}"' from within
> a recipe.
>
> Any ideas why or how this is getting unset, and how to fix?
> I couldn't find any documentation that talks about this.
>
> Thanks
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
next prev parent reply other threads:[~2014-07-09 23:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 20:58 Environment Variables being unset by bitbake? Allen Kennedy Jr.
2014-07-09 23:11 ` Patrick Doyle [this message]
2014-07-10 8:29 ` Nicolas Dechesne
2014-07-10 13:46 ` Allen Kennedy Jr.
2014-07-10 13:58 ` Nicolas Dechesne
[not found] ` <CAO-21LM=ucVNUPAwDgXA5FkB0dsi=ASQrgTSAaq+fFRhhkWaRA@mail.gmail.com>
2014-07-10 14:23 ` Nicolas Dechesne
2014-07-10 14:29 ` Allen Kennedy Jr.
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=CAF_dkJA_5nbzfAA02_CCxmEZ3vJjjQXYXqFRhV_HsmyuuuPuiA@mail.gmail.com \
--to=wpdster@gmail.com \
--cc=allen@kennedystuff.com \
--cc=yocto@yoctoproject.org \
/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.