From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/6] scripts/bitbake: ensure user is in build directory
Date: Thu, 15 Mar 2012 01:30:31 +0100 [thread overview]
Message-ID: <4F613827.3040705@opendreambox.org> (raw)
In-Reply-To: <e4d001f8c6f8945c8c70c2558ad5f9e1fd85dfad.1331685330.git.paul.eggleton@linux.intel.com>
Hello Paul,
On 14.03.2012 01:36, Paul Eggleton wrote:
> If the user is in any directory other than $BUILDDIR when the bitbake
> wrapper script is run, then show an error an exit.
this patch broke my setup.
My $BUILDDIR points to tmp, so that pseudo doesn't get rebuilt for every
machine. I have a shared tmp for many machines.
BUILDDIR doesn't seem to have any other use than pointing to the
'pseudodone' file. I don't understand why it's required to run bitbake
from there.
I'm using a tiny shell fragment to set up my build environment. This is
how it looks like:
export BUILDDIR=${PREFIX}/tmp
export
PATH=${PREFIX}/openembedded-core/scripts:${PREFIX}/bitbake/bin:${PATH}
local.conf and bblayers.conf for individual machines are stored in
${PREFIX}/build/${MACHINE}/conf.
Regards,
Andreas
> Fixes [YOCTO #2071].
>
> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> ---
> scripts/bitbake | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/scripts/bitbake b/scripts/bitbake
> index dda3b26..45c8697 100755
> --- a/scripts/bitbake
> +++ b/scripts/bitbake
> @@ -47,6 +47,11 @@ float_test() {
> # but earlier versions do not
> float_test "$TARVERSION > 1.23" && needtar="0"
>
> +if [ "`pwd`" != "$BUILDDIR" ] ; then
> + echo "BitBake must be run from your build directory: $BUILDDIR"
> + exit 1
> +fi
> +
> buildpseudo="1"
> if [ $needpseudo = "1" ] && [ -e "$BUILDDIR/pseudodone" ]; then
> PSEUDOBINDIR=`cat $BUILDDIR/pseudodone`
next prev parent reply other threads:[~2012-03-15 0:39 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 0:36 [PATCH 0/6] Misc build failure fixes Paul Eggleton
2012-03-14 0:36 ` [PATCH 1/6] scripts/bitbake: ensure user is in build directory Paul Eggleton
2012-03-14 14:52 ` Darren Hart
2012-03-14 15:09 ` Paul Eggleton
2012-03-14 15:19 ` Darren Hart
2012-03-15 0:30 ` Andreas Oberritter [this message]
2012-03-15 23:09 ` Paul Eggleton
2012-03-16 0:20 ` Andreas Oberritter
2012-03-16 10:56 ` Paul Eggleton
2012-03-16 11:55 ` VIJAY KUMAR
2012-03-16 12:19 ` Paul Eggleton
2012-03-18 15:07 ` Andreas Oberritter
2012-04-02 20:00 ` Khem Raj
2012-04-02 20:12 ` Paul Eggleton
2012-04-02 20:32 ` Chris Larson
2012-04-02 20:56 ` Paul Eggleton
2012-03-14 0:36 ` [PATCH 2/6] pulseaudio: add X library dependencies Paul Eggleton
2012-03-14 0:36 ` [PATCH 3/6] gst-plugins-bad: disable directfb in configure Paul Eggleton
2012-03-14 0:36 ` [PATCH 4/6] mx: add dependencies Paul Eggleton
2012-03-14 0:36 ` [PATCH 5/6] ncurses: fix build when ENABLE_WIDEC is not set Paul Eggleton
2012-03-14 14:52 ` Darren Hart
2012-03-14 0:36 ` [PATCH 6/6] linux-yocto-tiny: add dependency on xz-native Paul Eggleton
2012-03-14 8:21 ` Koen Kooi
2012-03-14 8:32 ` Paul Eggleton
2012-03-14 12:29 ` Bruce Ashfield
2012-03-14 12:39 ` Paul Eggleton
2012-03-14 12:59 ` Bruce Ashfield
2012-03-14 13:03 ` Paul Eggleton
2012-03-14 13:12 ` Bruce Ashfield
2012-03-14 14:55 ` Darren Hart
2012-03-14 13:18 ` [PATCH 0/6] Misc build failure fixes Richard Purdie
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=4F613827.3040705@opendreambox.org \
--to=obi@opendreambox.org \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox