All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: ISO-Codes Build Failing
Date: Mon, 08 Aug 2011 20:54:51 -0700	[thread overview]
Message-ID: <4E40AF8B.4080103@gmail.com> (raw)
In-Reply-To: <1312858153686306500@rkmorris.us>

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

On 08/08/2011 07:49 PM, Russell Morris wrote:
> Hi,
> 
> I have been trying to build angstrom-x-image, but it fails - at
> iso-codes. The issue may be because Verizon FIOS is now blocking FTP
> (as more and more ISP's are), but in any case I created a new recipe
> to correct this (and it works). How do I get this change in to the
> official OpenEmbedded build (or can I even?)?
> 
> Also ... what is the official OE path? I admit, now with
> OpenEmbedded, core, etc. - it's getting a bit confusing ... :-(. It
> really seems like (base?) OpenEmbedded is getting quite out of date,
> but I could be wrong.
> 

send patches for meta-openembedded to add the recipe that will make it
into the new layered metadata based distros.


> On to gs next (which seems to be failing during the do_configure
> stage).
> 
> Thanks, ... Russell
> 
> _______________________________________________ Openembedded-devel
> mailing list Openembedded-devel@lists.openembedded.org 
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


- --
> 
- -Khem
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk5Ar4sACgkQuwUzVZGdMxQEYgCffYNw/R3mvw8XZQ8NkOxqKKgO
Nv0An0g0n9S6r/vW/vKG0HrZ5ktvEgQu
=HSTm
-----END PGP SIGNATURE-----



  reply	other threads:[~2011-08-09  3:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-09  2:49 ISO-Codes Build Failing Russell Morris
2011-08-09  3:54 ` Khem Raj [this message]
2011-08-10  0:42   ` Russell Morris
2011-08-21 21:57     ` Russell Morris

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=4E40AF8B.4080103@gmail.com \
    --to=raj.khem@gmail.com \
    --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.