From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: DEPLOY_DIR / packaged staging / persistent toolchains
Date: Tue, 07 Apr 2009 13:43:51 -0400 [thread overview]
Message-ID: <20090407174351.GD11203@denix.org> (raw)
In-Reply-To: <200904071212.18247.mickey@vanille-media.de>
On Tue, Apr 07, 2009 at 12:12:18PM +0200, Michael 'Mickey' Lauer wrote:
> Hi folks,
>
> I just stumbled over something that surprises me. I have set DEPLOY_DIR
> outside TMP for a while (which works fine). Now when I remove the TMPDIR to
> start a new build from scratch, I can no longer build anything. Apparantly OE
> thinks I do no longer need a toolchain, since it does not attempt to built
> one. I need to remove the whole DEPLOY_DIR to be able to do any builds again.
>
> Wasn't the idea of packaged staging to be able to keep core packages and the
> toolchain intact when removing TMPDIR? If I understodd this wrong, how can I
> do something like that these days? Would it be sufficient to set CROSS_DIR
> outside TMPDIR?
Mickey,
Are you overwriting DEPLOY_DIR_PSTAGE from its default ${DEPLOY_DIR}/pstage?
Otherwise it should work and should populate CROSS_DIR from pstage. There is
one little quirk - if you don't have opkg in your system PATH, you may need to
remove opkg packages from pstage to force rebuilding and installing it. Its a
chicken and egg problem - opkg-native binary is in .ipk and in order to
install and use it you need opkg-native...
--
Denys
next prev parent reply other threads:[~2009-04-07 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 10:12 DEPLOY_DIR / packaged staging / persistent toolchains Michael 'Mickey' Lauer
2009-04-07 17:43 ` Denys Dmytriyenko [this message]
2009-04-07 18:16 ` Koen Kooi
2009-04-07 18:49 ` Denys Dmytriyenko
2009-04-07 19:10 ` Koen Kooi
2009-04-07 22:39 ` Michael 'Mickey' Lauer
2009-04-07 23:18 ` Denys Dmytriyenko
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=20090407174351.GD11203@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@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 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.