openembedded-devel.lists.openembedded.org archive mirror
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: should beagleboard-demo-image (b-d-i) be theoretically buildable?
Date: Mon, 26 Jul 2010 13:30:48 +0200	[thread overview]
Message-ID: <i2jrl9$4j3$1@dough.gmane.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1007260653230.5356@lynx>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

It builds fine on all the buildhosts I have (ubuntu 8.04-32bit,
9.10-64bit, debian testing-64bit among others).

And I see no logs attached to your email, so I can't help.

On 26-07-10 12:57, Robert P. J. Day wrote:
> 
>   been trying to keep up with the recent reorg so a quick question --
> i was just about to clean and try a rebuild of b-d-i on my 64-bit
> ubuntu 10.04 system.  should that work?
> 
>   i ask this since, a few days ago, during a test build, i was
> surprised to note that, finally, abiword built but (sadly) firefox was
> back to being unbuildable.  so i'm never sure what to *expect*.  if i
> try to build from scratch, should i expect success right now?  i'm
> going to start the rebuild, anyway.
> 
> rday
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMTXHoMkyGM64RGpERAqcSAKCgDwqqML5/QpbAwbFtYuotDcGoXACgllxl
rIk5bHacyPx9eU1Sm0S6RXU=
=g076
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-07-26 11:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-26 10:57 should beagleboard-demo-image (b-d-i) be theoretically buildable? Robert P. J. Day
2010-07-26 11:30 ` Koen Kooi [this message]
2010-07-26 11:46   ` Robert P. J. Day
2010-08-01 22:39     ` Khem Raj
2010-08-02 14:15       ` Philip Balister
2010-08-03 23:53         ` 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='i2jrl9$4j3$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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;
as well as URLs for NNTP newsgroup(s).