Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: MIPS vs MIPS32 tunings -- summary and questions
Date: Wed, 18 Apr 2012 13:00:26 +0100	[thread overview]
Message-ID: <1334750426.24091.73.camel@ted> (raw)
In-Reply-To: <20120418115428.GJ3635@jama.jama.net>

On Wed, 2012-04-18 at 13:54 +0200, Martin Jansa wrote:
> On Wed, Apr 18, 2012 at 01:45:54PM +0200, Andreas Oberritter wrote:
> > On 18.04.2012 13:40, Richard Purdie wrote:
> > > On Wed, 2012-04-18 at 13:30 +0200, Andreas Oberritter wrote:
> > >> now, after having repacked all binary tarballs that had mipsel or
> > >> mipsel-nf in their name and contents, and after having changed all
> > >> occurrences of mipsel and mipsel-nf in my local recipes (where
> > >> appropriate), and after having rebuilt everything from scratch again, it
> > >> came to my attention that "mipsel" in PACKAGE_EXTRA_ARCHS breaks opkg,
> > >> because no mipsel packages are being generated. That's what I told
> > >> before, right?
> > > 
> > > How is this breaking opkg? We often have architectures listed in there
> > > for which there are no packages generated (all, noarch and any spring to
> > > mind)?
> > 
> > Downloading http://10.0.0.1/mipsel/Packages.gz.
> > wget: server returned error: HTTP/1.1 404 Not Found
> > Collected errors:
> >  * opkg_download: Failed to download http://10.0.0.1/mipsel/Packages.gz, wget returned 1.
> 
> I had a lot of those (e.g. because armv7a-vfp-neon was including 20
> arm*feed.conf variants in /etc/opkg most of them empty - without
> Packages.gz).
> 
> So I've added "filter" to distro-feed-configs
> http://git.shr-project.org/git/?p=meta-smartphone.git;a=commit;h=236aa553bb0f82f741c6edb793e96f421f24f4fa
> to add only feeds I'm generating (and I also don't want armv5* packages
> installed on armv7a-vfp-neon target unless user explicitly adds armv5*
> feed).

This is the better solution. I think we need to get a better default
feed-config generation mechanism into the core. Distros may still need
to tweak it but it would be good to share some of the best practises...

Cheers,

Richard




  reply	other threads:[~2012-04-18 12:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10 17:53 MIPS vs MIPS32 tunings -- summary and questions Mark Hatle
2012-04-10 19:28 ` Andreas Oberritter
2012-04-16 13:55   ` Andreas Oberritter
2012-04-16 14:37     ` Robert Yang
2012-04-16 15:23       ` Andreas Oberritter
2012-04-16 15:50       ` Richard Purdie
2012-04-16 14:42     ` Richard Purdie
2012-04-16 15:15       ` Andreas Oberritter
2012-04-16 15:30         ` Mark Hatle
2012-04-18 11:30           ` Andreas Oberritter
2012-04-18 11:40             ` Richard Purdie
2012-04-18 11:45               ` Andreas Oberritter
2012-04-18 11:53                 ` Andreas Oberritter
2012-04-18 11:54                 ` Martin Jansa
2012-04-18 12:00                   ` Richard Purdie [this message]
2012-04-18 12:08                     ` Andreas Oberritter
2012-04-18 12:45                       ` Richard Purdie
2012-04-18 14:37                         ` Andreas Oberritter
2012-04-18 15:21                           ` Mark Hatle
2012-04-18 15:46                             ` Martin Jansa
2012-04-18 17:01                               ` Koen Kooi
2012-04-18 18:10                                 ` Andreas Oberritter
2012-04-18 18:31                                   ` Koen Kooi
2012-04-18 19:57                                 ` Martin Jansa
2012-04-18 12:15                     ` Koen Kooi

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=1334750426.24091.73.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@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