From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OpenEmbedded Development mailing list
<openembedded-devel@lists.openembedded.org>
Subject: FYI, beagleboard-demo-image now builds on fedora 12
Date: Sat, 21 Nov 2009 09:54:45 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.0911210951280.5624@localhost> (raw)
for anyone who cares, i can now build beagleboard-demo-image from
scratch on my (effectively) f12 system, so i'm happy. but it might
be worth watching out for other packages that will fail because of
that cpp linemarkers issue. so far, so good, though, and thanks to
everyone for their patience.
rday
p.s. out of curiosity, if i just finished a build and *immediately*
do the same build again, it appears to rerun the last 3 or 4 steps,
which on this system takes *many* minutes. those steps represent, uh,
rebuilding the root filesystem? if nothing's changed, why is that
work being repeated?
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
reply other threads:[~2009-11-21 14:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.0911210951280.5624@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.