From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] dosfstools-2.11: Fix memory leak in mkdosfs
Date: Sun, 09 Aug 2015 22:30:32 +0100 [thread overview]
Message-ID: <6888320.kH9hAkXKUb@peggleto-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <CAMKF1srqaXwG8v+FJz0G2M3ys9ArcWD1fkX_7h3F8z1AZqi3oA@mail.gmail.com>
On Sunday 09 August 2015 10:03:25 Khem Raj wrote:
> On Aug 9, 2015 9:21 AM, "Paul Eggleton" <paul.eggleton@linux.intel.com>
> wrote:
> > On Saturday 08 August 2015 11:54:45 Khem Raj wrote:
> > > > On Aug 7, 2015, at 12:54 PM, Paul Eggleton <
> paul.eggleton@linux.intel.com>
> > > > wrote:>
> > > >
> > > > On Friday 07 August 2015 12:26:56 Khem Raj wrote:
> > > >>> On Aug 7, 2015, at 2:51 AM, Paul Eggleton
> > > >>> <paul.eggleton@linux.intel.com>
> > > >>> wrote:>
> > > >> devtool modify dosfstools -x ~/projects/dosfstools
> > > >> ERROR: This script can only be run after initialising the build
> > > >> environment
> > > >> (e.g. by using oe-init-build-env)
> > > >>
> > > >> so is it must now to use the setup script ? or can be extract some
> > > >> needed setup from it to let it work with setups not using the init
> > > >> script
> > > >
> > > > Well it needs to be able to run bitbake internally (directly and using
> > > > tinfoil), hence the need to have the environment set up to do so. I
> > > > don't really see a way around that.
> > >
> > > Then limited use of devtool should be documented as available
> >
> > How is this limited? It operates under the same conditions as bitbake
> > itself does.
>
> Your last email indicated as if it always needs internal build environment.
> If that's not the case then it's what I was requesting for the settings
> that are required to execute it provided bitbake is in path and is building
> fine but it's not using the settings provided by setup environment script
There aren't any special settings though - if you can run bitbake, you should
be able to run devtool. If you're getting the error you pasted, it's because
BUILDDIR is not set.
I just fetched Angstrom's setup-scripts, checked out the angstrom-v2015.06-
yocto1.8 branch, and ran through the steps mentioned in the README.
Unfortunately it didn't check out all the layers successfully (someone should
probably look at that...) once I tweaked bblayers.conf to remove the missing
layers, devtool ran just fine. (Of course as part of setting up I had run
. environment-angstrom - you are doing that, right?)
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2015-08-09 21:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 9:06 [meta-oe][PATCH] dosfstools-2.11: Fix memory leak in mkdosfs Amarnath Valluri
2015-08-06 9:12 ` Alexander Kanavin
2015-08-06 9:25 ` Paul Eggleton
2015-08-06 12:17 ` Valluri, Amarnath
2015-08-07 2:52 ` Khem Raj
2015-08-07 9:51 ` Paul Eggleton
2015-08-07 19:26 ` Khem Raj
2015-08-07 19:54 ` Paul Eggleton
2015-08-08 18:54 ` Khem Raj
2015-08-09 16:21 ` Paul Eggleton
2015-08-09 17:03 ` Khem Raj
2015-08-09 21:30 ` Paul Eggleton [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=6888320.kH9hAkXKUb@peggleto-mobl.ger.corp.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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.