Openembedded Core Discussions
 help / color / mirror / Atom feed
From: mark gross <markgross@thegnar.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Tell me your build error message annoyances!
Date: Tue, 31 May 2011 18:34:52 -0700	[thread overview]
Message-ID: <20110601013452.GA12171@gvim.org> (raw)
In-Reply-To: <4DE56B0D.4020209@intel.com>

On Tue, May 31, 2011 at 03:26:21PM -0700, Scott Garman wrote:
> Hey folks,
> 
> I'd like to collect some feedback on error messages while building
> that you find confusing/annoying/unhelpful. I'm going to be working
> on trying to improve the situation and would like to hear from you
> about what could be more helpful.


You can make SkipPackage print out what recipes is getting skipped!  I
blew a bunch of time trying to build qemu64 minimal target before I
found that you need the meta-intel layer such that grub 2 would be
provided.  Recipes-bsp has grub 0.97 but, it raises a SkipPackage
exception if the target is not 32 bit.

bitbake -DDD grub would report NoProvider: grub  Yet show the
grub_0.97.bb was indeed getting processed.

--mark



> 
> I'm starting to track some of these situations with the following bugs:
> 
> http://bugzilla.pokylinux.org/show_bug.cgi?id=542
> 
> http://bugzilla.pokylinux.org/show_bug.cgi?id=1127
> 
> http://bugzilla.pokylinux.org/show_bug.cgi?id=1128
> 
> I can't promise to fix everything you come up with, but I'd like to
> try to make a dent in some of these issues and improve the usability
> of our build system.
> 
> Thanks,
> 
> Scott
> 
> -- 
> Scott Garman
> Embedded Linux Engineer - Yocto Project
> Intel Open Source Technology Center
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core



  reply	other threads:[~2011-06-01  1:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31 22:26 Tell me your build error message annoyances! Scott Garman
2011-06-01  1:34 ` mark gross [this message]
2011-06-01 15:06 ` Phil Blundell
2011-06-01 16:25   ` Richard Purdie
2011-06-01 16:58     ` Chris Larson
2011-06-03 14:35     ` mark gross
2011-06-03 14:48       ` Paul Eggleton
2011-06-02 14:17   ` Phil Blundell
2011-06-02  7:34 ` Martin Jansa
2011-06-03  6:10 ` Darren Hart
2011-06-03  8:11   ` Richard Purdie
2011-06-03 14:22   ` Mark Hatle
2011-06-03 15:43     ` Phil Blundell
2011-06-03 15:47       ` Chris Larson
2011-06-07  4:53         ` Darren Hart
2011-06-07  9:18           ` Richard Purdie
2011-06-06 21:13   ` Scott Garman
2011-06-03 14:57 ` Koen Kooi
2011-06-09 11:02 ` Phil Blundell
2011-06-09 11:17   ` Richard Purdie
2011-06-09 15:00 ` Scott Garman

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=20110601013452.GA12171@gvim.org \
    --to=markgross@thegnar.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