From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@lists.openembedded.org
Subject: Re: apparently, i have a beagleboard-demo-image!
Date: Mon, 16 Nov 2009 11:51:18 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0911161148030.9291@localhost> (raw)
In-Reply-To: <4B017271.5040209@balister.org>
On Mon, 16 Nov 2009, Philip Balister wrote:
> On 11/16/2009 10:34 AM, Robert P. J. Day wrote:
> >
> > build just finished, 0 errors. go figure. but i'm puzzled
> > since, until recently, guile-native was failing to build and i
> > don't see anything in the git log that would have done anything
> > with that package. can someone clarify this? i also don't recall
> > manually patching that package based on an earlier poster's
> > suggestion, so i have no idea why it would suddenly start to
> > build. (perhaps i'll distclean that and make sure it builds
> > again.)
> >
> > in any event, happy happy, joy joy.
>
> Lucky you, opkg-cl is failing for me. Fortunately, I have some real
> work to keep me out of trouble.
well, crap. so i distclean'ed guile-native and just tried to
re-bitbake it -- same build error as before. i have no idea how i got
past that during this last build of beagleboard-demo-image. i'm
confused.
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-16 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 15:34 apparently, i have a beagleboard-demo-image! Robert P. J. Day
2009-11-16 15:40 ` Philip Balister
2009-11-16 16:03 ` Robert P. J. Day
2009-11-16 16:51 ` 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.0911161148030.9291@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 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.