Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: MIPS vs MIPS32 tunings -- summary and questions
Date: Wed, 18 Apr 2012 13:53:24 +0200	[thread overview]
Message-ID: <4F8EAB34.3070705@opendreambox.org> (raw)
In-Reply-To: <4F8EA972.1090304@opendreambox.org>

On 18.04.2012 13:45, 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.

That is, because although noarch and any are part of ${PACKAGE_ARCHS},
they are not part of ${PACKAGE_EXTRA_ARCHS}.

distro-feed-configs.bb uses "all ${PACKAGE_EXTRA_ARCHS} ${MACHINE_ARCH}".

Regards,
Andreas



  reply	other threads:[~2012-04-18 12:03 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 [this message]
2012-04-18 11:54                 ` Martin Jansa
2012-04-18 12:00                   ` Richard Purdie
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=4F8EAB34.3070705@opendreambox.org \
    --to=obi@opendreambox.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