From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Bryan Evenson <bevenson@melinkcorp.com>
Cc: poky@yoctoproject.org
Subject: Re: Errors attempting to build AT91SAM9x5 BSP
Date: Tue, 13 Nov 2012 17:10:46 +0000 [thread overview]
Message-ID: <7874249.T1W7SIhH85@helios> (raw)
In-Reply-To: <91586D499ADFD74FBCFB8425266A5DE4012C7CF327A4@pluto.melinkcorp.local>
On Tuesday 13 November 2012 11:26:08 Bryan Evenson wrote:
> I decided to start over with the stable danny tarball instead of using the
> Git repository. I've been able to build a core-image-minimal QEMU image
> and run it in QEMU. After that I created my new BSP using the yocto-bsp
> script and added my new BSP to the build/conf/bblayers.conf file as
> directed in the BSP Guide. However, now whenever I try to use bitbake for
> anything I get the error message "NOTE: Your conf/bblayers.conf has been
> automatically updated. Please re-run bitbake." I've tried incrementing the
> LCONF_VERSION variable in conf/bblayers.conf and incrementing the
> CONF_VERSION in conf/local.conf. I've also tried issuing "bitbake -f -c
> clean core-image-minimal" and I get the same error. The only way I've been
> able to use bitbake again is to remove the line for my new BSP from the
> BBLAYERS variable in conf/bblayers.conf.
What value was LCONF_VERSION at before you removed it? Also, could you send
your bblayers.conf file?
Thanks,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-11-13 17:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 18:27 Errors attempting to build AT91SAM9x5 BSP Bryan Evenson
2012-11-13 16:26 ` Bryan Evenson
2012-11-13 17:10 ` Paul Eggleton [this message]
2012-11-13 17:46 ` Bryan Evenson
2012-11-13 17:52 ` Paul Eggleton
2012-11-13 19:17 ` Bryan Evenson
2012-11-15 11:03 ` Paul Eggleton
2012-11-19 16:35 ` Bryan Evenson
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=7874249.T1W7SIhH85@helios \
--to=paul.eggleton@linux.intel.com \
--cc=bevenson@melinkcorp.com \
--cc=poky@yoctoproject.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.