Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: open embedded build issues with beagle board
Date: Tue, 08 Jul 2014 12:11:33 -0400	[thread overview]
Message-ID: <53BC1835.90204@balister.org> (raw)
In-Reply-To: <CAD2C2VT=3DipX=8chChc6_NefZSfs3jocmYxePJp5THxANiKVg@mail.gmail.com>

On 07/08/2014 02:54 AM, Bryan wrote:
> Hi All
>  I am trying to build  Openembeeded classic for Beagle board-XM but i am
> getting lot of broken link issues. I have  set DISTRO as angstrom-2010.x in
> local.conf.   Is this approach  ok? or should i move to openembedded core ??
> Pls suggest.

Use the current Angstrom instructions, oe-classic is pretty much
completely unsupported now.

Philip

> 
> Broken link e.g.
> 
> Resolving www.angstrom-distribution.org (www.angstrom-distribution.org)...
> 140.211.169.177
>  Connecting to www.angstrom-distribution.org
> (www.angstrom-distribution.org)|140.211.169.177|:80...
> connected.
>  HTTP request sent, awaiting response...
> 404 Not Found  2014-07-08 10:13:43 ERROR 404: Not Found.
> 
> Thanks in advance
> 


  parent reply	other threads:[~2014-07-08 16:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08  6:54 open embedded build issues with beagle board Bryan
2014-07-08 14:47 ` Cliff Brake
2014-07-08 16:11 ` Philip Balister [this message]
2014-07-11  6:00   ` Bryan
2014-07-11 13:11     ` Cliff Brake
2014-07-15  4:29     ` Bryan
2014-07-15  6:04       ` Stephen Arnold
     [not found]       ` <53C51AE2.4030100@bec-systems.com>
     [not found]         ` <CAD2C2VR22ww51=1UQbW7OxtWvr8dV1PjLhr0d0O176JtX6PJKQ@mail.gmail.com>
2014-07-17  6:59           ` Bryan
2014-07-17  7:05             ` Henning Heinold
2014-07-17  7:14               ` Stephen Arnold
2014-07-22 10:15           ` Bryan
2014-07-23  1:10             ` Stephen Arnold

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=53BC1835.90204@balister.org \
    --to=philip@balister.org \
    --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