Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Jaap de Jong <jaap.dejong@nedap.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: opkg : angstrom fails console-image build
Date: Thu, 22 Jul 2010 08:17:41 +0200	[thread overview]
Message-ID: <4C47E285.708@nedap.com> (raw)
In-Reply-To: <AANLkTimMZU5mXUn1ZSFJ0_8aDu8ykWYDXMD55iZW8s7A@mail.gmail.com>

I've made a completely clean build last night and it breaks at the same 
problem.


> You have an 'opkg' package and an 'opkg-nogpg-nocurl' package. As far
> as I can tell, if you had built from a clean dev tree then there would
> be no 'opkg' package. Angstrom currently uses opkg-nogpg-nocurl, so
> that is the only package you should have.
>
> This indicates that you have a non clean dev tree, or have had a non
> clean dev tree in the past. If you've done a build in the past with
> patches applied, then you've reverted the patches, you probably need
> to remove your temp dir and start the build again.
>
> -Graham
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>    



  reply	other threads:[~2010-07-22  6:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-21 14:31 opkg : angstrom fails console-image build Marco Cavallini
2010-07-21 16:05 ` Koen Kooi
2010-07-21 20:38   ` Marco Cavallini
2010-07-22  0:03     ` Graham Gower
2010-07-22  6:17       ` Jaap de Jong [this message]
2010-07-22  7:11         ` Graham Gower
2010-07-22  7:26           ` Graham Gower
2010-07-22  9:36             ` Martin Jansa

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=4C47E285.708@nedap.com \
    --to=jaap.dejong@nedap.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox