All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex J Lennon <ajlennon@dynamicdevices.co.uk>
To: yocto@yoctoproject.org
Subject: Re: Basic failures building 1st Yocto Project and Yocto Raspberry Pi
Date: Thu, 03 Jan 2013 10:57:35 +0000	[thread overview]
Message-ID: <50E5641F.9050301@dynamicdevices.co.uk> (raw)
In-Reply-To: <50E5620A.3070208@communistcode.co.uk>

On 03/01/2013 10:48, Jack Mitchell wrote:
> On 02/01/13 21:47, David Evans wrote:
>> Dear Sirs,
>>
>> I apologise for asking this question to everyone, but I can't figure 
>> out who best to direct this question to.
>>
>> When I build the standard Yocto Project in the Quick-Start guide I get 
>> the following Warnings.
>>
>> WARNING: Failed to fetch URL 
>> http://www.apache.org/dist/subversion/subversion-1.7.6.tar.bz2, 
>> attempting MIRRORS if available
>> WARNING: Failed to fetch URL 
>> ftp://ftp.ossp.org/pkg/lib/uuid/uuid-1.6.2.tar.gz, attempting MIRRORS 
>> if available
>> WARNING: Failed to fetch URL 
>> http://downloads.sourceforge.net/project/libpng/libpng12/1.2.49/libpng-1.2.49.tar.bz2, 
>> attempting MIRRORS if available
>>
>> As a complete Newbie to Yocto, having the Quick-Start fail like this 
>> is killing me, as I have no stable example upon which to build my 
>> under standing.
>>
>> My ultimate goal is to run the Raspberry Pi project as outlined at 
>> http://www.pimpmypi.com/blog/blogPost.php?blogPostID=7, but I am 
>> seeing the same do_fetch failures as those reported by Ed Nelson at 
>> https://lists.yoctoproject.org/pipermail/yocto/2013-January/013571.html.
>>
>> Any help will be much appreciated.
>>
>>
>> Regards,
>>
>> David
>>
>>
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
> 
> I will try to get round to updating this tutorial soon; as it has become 
> a bit dated - however as Alex mentions it should still work fine albeit 
> with a few warnings due to unavailable sources.
> 
> It should just be a matter of changing a few git revisions, and tweaking 
> the wording a bit to involve the new meta-yocto, meta-yocto-bsp split. 
> If anyone wishes to step up to the plate the source for this blog post 
> is available at [1] and I will happily accept patches.
> 
> Cheers,
> Jack.
> 
> [1] https://github.com/CommunistCode/PimpMyPi-Community-Blog-Posts
> 

Jack,

I found that post hugely helpful thanks, as I'd tried some months before
with the information at Distant Earth (http://www.distant-earth.com/wp/)
and for some reason I just wasn't able to produce an image that booted
on the RPi.

As you mention, I did find those git commits to be a little old and I
wasn't able to get an EFL UI build working from them.

As a result I migrated forward to the latest head commits at the time
and was able to get a build going (running EFL in fact)

I put some notes up here as I went along, which build upon the Pimp My
Pi blog post -

https://www.assembla.com/spaces/ciseco-eve/wiki/Getting_Started

I haven't yet updated those notes to reflect the newer Git commits I was
using but I've noted them down here -

https://www.assembla.com/spaces/ciseco-eve/wiki/Work_in_progress

Not sure if that helps, except that I can say it is building and working
from these much more recent commits...

(On a separate note I'd be interested in a chat with anybody who has any
ideas on performance of EFL and how it can be improved, e.g. improved
XServer support, hard fp perhaps, maybe EFL on DirectFB or similar?)

Cheers,

Alex


  reply	other threads:[~2013-01-03 10:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-02 21:47 Basic failures building 1st Yocto Project and Yocto Raspberry Pi David Evans
2013-01-02 21:55 ` Gary Thomas
2013-01-02 22:06   ` Alex J Lennon
2013-01-02 23:17   ` Saul Wold
2013-01-03 10:48 ` Jack Mitchell
2013-01-03 10:57   ` Alex J Lennon [this message]
2013-01-05  1:06   ` Alex J Lennon
2013-01-05 18:09     ` Jack Mitchell

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=50E5641F.9050301@dynamicdevices.co.uk \
    --to=ajlennon@dynamicdevices.co.uk \
    --cc=yocto@yoctoproject.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.