From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@lists.openembedded.org
Subject: Re: building versus just using native guile?
Date: Thu, 19 Nov 2009 12:46:52 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0911191245280.13430@localhost> (raw)
In-Reply-To: <4B040BB5.20308@balister.org>
On Wed, 18 Nov 2009, Philip Balister wrote:
> Can you remind me what distro you are using on your build machine?
> Normally, I seem to share your pain, but beagle-demo-image is
> building for me at the moment. (I'm basically wiping tmp and
> starting over as fast as i can atm)
the prognosis:
https://bugzilla.redhat.com/show_bug.cgi?id=538707
see comment 3.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
prev parent reply other threads:[~2009-11-19 17:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 14:40 building versus just using native guile? Robert P. J. Day
2009-11-18 14:59 ` Philip Balister
2009-11-18 15:22 ` Robert P. J. Day
2009-11-19 17:46 ` Robert P. J. Day [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=alpine.LFD.2.00.0911191245280.13430@localhost \
--to=rpjday@crashcourse.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox