From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Cc: Using OE <openembedded-users@openembedded.org>
Subject: Re: [oe-users] ERROR: function do_stage failed
Date: Fri, 14 Sep 2007 09:57:25 +0100 [thread overview]
Message-ID: <1189760245.6181.7.camel@localhost.localdomain> (raw)
In-Reply-To: <522721688.20070914040225@vanille-media.de>
On Fri, 2007-09-14 at 04:02 +0200, Dr. Michael Lauer wrote:
> The more Angstrom-specific hacks I see in OpenEmbedded, the more it
> scares me, because this means once someone wants a lean-and-mean way
> to compile a distro, he will run into lots of obstacles which --
> in my opinion -- should rather be solved in a distribution-independent way.
Can you give some examples of these as I wasn't aware of this :/
Cheers,
Richard
prev parent reply other threads:[~2007-09-14 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8e53a5920709112139s1b54c4cdsdb27b0df1995399e@mail.gmail.com>
[not found] ` <7215-66668@sneakemail.com>
[not found] ` <8742-19702@sneakemail.com>
[not found] ` <164986939.20070914021814@vanille-media.de>
[not found] ` <46E9D4BA.3080708@balister.org>
2007-09-14 2:02 ` [oe-users] ERROR: function do_stage failed Dr. Michael Lauer
2007-09-14 8:57 ` Richard Purdie [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=1189760245.6181.7.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
--cc=openembedded-users@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