This patch set clears up some of the warnings that are generated when
building baryon against the tip of the 1.3_M3 branch of poky.

The following changes since commit 500a124831e292d76d864a3c64a57a5007c4553a:

kernel: enable nfsd when using the 3.4 kernel (2012-09-13 10:43:26 -0700)

are available in the git repository at:

git://git.yoctoproject.org/poky-contrib strassek/baryon-warnings
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=strassek/baryon-warnings

Kevin Strasser (4):
proftpd: remove unused directories after install
samba: remove unused directories after install
orc: specify the generic licenses being used
talloc: specify the version of LGPL and include the license text

recipes-connectivity/samba/samba.inc | 2 ++
recipes-extended/proftpd/proftpd_1.3.4b.bb | 1 +
recipes-multimedia/orc/orc.inc | 2 +-
recipes-multimedia/orc/orc_0.4.5.bb | 2 +-
recipes-support/talloc/talloc_2.0.1.bb | 6 +++---
5 files changed, 8 insertions(+), 5 deletions(-)

--
1.7.9.5

On Thursday 27 September 2012 17:55:45 Evade Flow wrote:

Fair enough. And I should mention that the error I reported occurs on
Ubuntu 10.04. It's not like I wasn't warned. :-}

WARNING: Host distribution "Ubuntu 10.04 LTS" has not been validated
with this version of the build system; you may possibly experience
unexpected failures. It is recommended that you use a tested
distribution.

(Other than this oddity with the perl package, things seem to work fine.)

Yeah, it's just a warning :)

This issue is rather perplexing. We're supposed to not be using the host tar
if it is older than 1.24 due to another bug in earlier versions - if an older
version is found we build tar-replacement-native before anything else gets
built. Was tar-replacement-native built on the machine where it was failing?
You can verify it built by just checking under tmp/sysroots/<native
sysroot>/usr/bin/ to see if tar exists there.

Cheers,
Paul

--

Paul Eggleton
Intel Open Source Technology Centre

Fair enough. And I should mention that the error I reported occurs on
Ubuntu 10.04. It's not like I wasn't warned. :-}

WARNING: Host distribution "Ubuntu 10.04 LTS" has not been validated
with this version of the build system; you may possibly experience
unexpected failures. It is recommended that you use a tested
distribution.

(Other than this oddity with the perl package, things seem to work fine.)


On Thu, Sep 27, 2012 at 3:56 PM, Rifenbark, Scott M
<scott.m.rifenbark@...> wrote:

I was told that I hit the server at a busy time thus causing the fetch to fail. I just re-ran it and ran error free. I was also told this was a rare occurrence but it does happen.

Scott

-----Original Message-----
From: Evade Flow [mailto:evadeflow@...]
Sent: Thursday, September 27, 2012 12:42 PM
To: Rifenbark, Scott M
Cc: yocto@...
Subject: Re: [yocto] build failure on current

I'm new to Yocto, but I've seen similar errors that seem to be due to
differences in the version of tar on the build server. Everything's
fine on this machine:

good% tar --version
tar (GNU tar) 1.26

but I get CRC errors sometimes on this one:

bad% otp-mmes-build% tar --version
tar (GNU tar) 1.22

The specific recipe I was having problems with was, I think,
perl-native. I couldn't untar/uncompress the perl archive in
build/downloads with tar 1.22, but it worked fine with tar 1.26. (I
don't have a solution, sorry. Around the same time I noticed this, I
found out that the image I was building was supposed to be built on
the denzil branch, so I just switched over to denzil and the problem
went away.)


On Thu, Sep 27, 2012 at 3:20 PM, Rifenbark, Scott M
<scott.m.rifenbark@...> wrote:

I am running through the build example for the QS and hit a failure when
trying to access git://git.yoctoproject.org/libowl;protocol=git. I started
with the tarball here: http://autobuilder.yoctoproject.org/nightly/CURRENT

Full transcript.



srifenbark@scottrif-desktop:~$ cd
poky-0b09e50810162a07ef0aecee91ee32b4a36334a3
srifenbark@scottrif-desktop:~/poky-0b09e50810162a07ef0aecee91ee32b4a36334a3$
source oe-init-build-env
You had no conf/local.conf file. This configuration file has therefore been
created for you with some default values. You may wish to edit it to use a
different MACHINE (target hardware) or enable parallel build options to take
advantage of multiple cores for example. See the file for more information
as
common configuration options are commented.

The Yocto Project has extensive documentation about OE including a reference
manual
which can be found at:
http://yoctoproject.org/documentation

For more information about OpenEmbedded see their website:
http://www.openembedded.org/

You had no conf/bblayers.conf file. The configuration file has been created
for
you with some default values. To add additional metadata layers into your
configuration please add entries to this file.

The Yocto Project has extensive documentation about OE including a reference
manual
which can be found at:
http://yoctoproject.org/documentation

For more information about OpenEmbedded see their website:
http://www.openembedded.org/



### Shell environment set up for builds. ###

You can now run 'bitbake <target>'

Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
meta-toolchain-sdk
adt-installer
meta-ide-support

You can also run generated qemu images with a command like 'runqemu qemux86'

srifenbark@scottrif-desktop:~/poky-0b09e50810162a07ef0aecee91ee32b4a36334a3/build$
bitbake -k core-image-sato
Pseudo is not present but is required, building this first before the main
build
Parsing recipes: 100% |#########################################| Time:
00:00:48
Parsing of 825 .bb files complete (0 cached, 825 parsed). 1129 targets, 22
skipped, 0 masked, 0 errors.

Build Configuration:
BB_VERSION = "1.15.3"
TARGET_ARCH = "i586"
TARGET_OS = "linux"
MACHINE = "qemux86"
DISTRO = "poky"
DISTRO_VERSION = "1.2+snapshot-20120927"
TUNE_FEATURES = "m32 i586"
TARGET_FPU = ""
meta
meta-yocto
meta-yocto-bsp = "<unknown>:<unknown>"

NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 63 tasks of which 0 didn't need to be rerun
and all succeeded.
Loading cache: 100% |###########################################| ETA:
00:00:00
Loaded 1130 entries from dependency cache.

Build Configuration:
BB_VERSION = "1.15.3"
TARGET_ARCH = "i586"
TARGET_OS = "linux"
MACHINE = "qemux86"
DISTRO = "poky"
DISTRO_VERSION = "1.2+snapshot-20120927"
TUNE_FEATURES = "m32 i586"
TARGET_FPU = ""
meta
meta-yocto
meta-yocto-bsp = "<unknown>:<unknown>"

NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: validating kernel configuration

WARNING: The recipe is trying to install files into a shared area when those
files already exist. Those files are:

/home/scottrif/poky-0b09e50810162a07ef0aecee91ee32b4a36334a3/build/tmp/sysroots/x86_64-linux/usr/share/sgml/openjade-1.3.2/catalog
WARNING: The recipe is trying to install files into a shared area when those
files already exist. Those files are:

/home/scottrif/poky-0b09e50810162a07ef0aecee91ee32b4a36334a3/build/tmp/sysroots/qemux86/usr/include/python2.7/pyconfig.h

/home/scottrif/poky-0b09e50810162a07ef0aecee91ee32b4a36334a3/build/tmp/sysroots/qemux86/usr/lib/libpython2.7.so

/home/scottrif/poky-0b09e50810162a07ef0aecee91ee32b4a36334a3/build/tmp/sysroots/qemux86/usr/lib/libpython2.7.so.1.0

/home/scottrif/poky-0b09e50810162a07ef0aecee91ee32b4a36334a3/build/tmp/sysroots/qemux86/usr/lib/python2.7/config/Makefile
WARNING: Failed to fetch URL git://git.yoctoproject.org/libowl;protocol=git,
attempting MIRRORS if available
ERROR: Fetcher failure: Fetch command failed with exit code 2, output:

gzip: stdin: invalid compressed data--crc error

gzip: stdin: invalid compressed data--length error
tar: Skipping to next header
tar: Child returned status 1
tar: Error is not recoverable: exiting now

ERROR: Function failed: Fetcher failure for URL:
'git://git.yoctoproject.org/libowl;protocol=git'. Unable to fetch URL from
any source.
ERROR: Logfile of failure stored in:
/home/scottrif/poky-0b09e50810162a07ef0aecee91ee32b4a36334a3/build/tmp/work/i586-poky-linux/libowl-0.1+git1+6ebc8ac8f8575278dd40a535cadefa26374e44b1-r0/temp/log.do_fetch.1973
ERROR: Task 2306
(/home/scottrif/poky-0b09e50810162a07ef0aecee91ee32b4a36334a3/meta/recipes-sato/libowl/libowl_git.bb,
do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 5560 tasks of which 339 didn't need to be
rerun and 1 failed.

Summary: 1 task failed:

/home/scottrif/poky-0b09e50810162a07ef0aecee91ee32b4a36334a3/meta/recipes-sato/libowl/libowl_git.bb,
do_fetch
Summary: There were 3 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
srifenbark@scottrif-desktop:~/poky-0b09e50810162a07ef0aecee91ee32b4a36334a3/build$





Scott Rifenbark

Intel Corporation

Yocto Project Documentation

503.712.2702

503.341.0418 (cell)




_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto

I was told that I hit the server at a busy time thus causing the fetch to fail. I just re-ran it and ran error free. I was also told this was a rare occurrence but it does happen.

Scott

Something was bugging me about this, so I dug up my notes. I was wrong when I
said switching to denzil fixed my problem---it did NOT. I simply cannot
untar/uncompress the perl archive from CPAN with tar 1.22:

evadeflow% tar --version
tar (GNU tar) 1.22
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by John Gilmore and Jay Fenlason.
evadeflow% wget http://www.cpan.org/src/5.0/perl-5.14.2.tar.gz
--2012-09-27 15:45:23-- http://www.cpan.org/src/5.0/perl-5.14.2.tar.gz
Resolving usah1nprox1.al-lighting.com... 10.102.184.7
Connecting to usah1nprox1.al-lighting.com|10.102.184.7|:8080... connected.
Proxy request sent, awaiting response... 200 OK
Length: 15223598 (15M) [application/x-gzip]
Saving to: `perl-5.14.2.tar.gz'

100%[================================================================>]
15,223,598 480K/s in 31s

2012-09-27 15:45:55 (478 KB/s) - `perl-5.14.2.tar.gz' saved [15223598/15223598]

evadeflow% tar xf perl-5.14.2.tar.gz

gzip: stdin: invalid compressed data--crc error
tar: Child returned status 1
tar: Exiting with failure status due to previous errors


The way I 'fixed' this was to unpack/repack the archive on my other build
machine (the one with tar 1.26), copy the resultant 'perl-5.14.2' folder to
the original machine, retar/compress it with tar 1.22, and place this new
perl-5.14.2.tar.gz file in my pre-mirror folder.

Anyway, this seems just weird enough that I thought I should mention it on the
list...

I'm new to Yocto, but I've seen similar errors that seem to be due to
differences in the version of tar on the build server. Everything's
fine on this machine:

good% tar --version
tar (GNU tar) 1.26

but I get CRC errors sometimes on this one:

bad% otp-mmes-build% tar --version
tar (GNU tar) 1.22

The specific recipe I was having problems with was, I think,
perl-native. I couldn't untar/uncompress the perl archive in
build/downloads with tar 1.22, but it worked fine with tar 1.26. (I
don't have a solution, sorry. Around the same time I noticed this, I
found out that the image I was building was supposed to be built on
the denzil branch, so I just switched over to denzil and the problem
went away.)


On Thu, Sep 27, 2012 at 3:20 PM, Rifenbark, Scott M
<scott.m.rifenbark@...> wrote:

I am running through the build example for the QS and hit a failure when
trying to access git://git.yoctoproject.org/libowl;protocol=git. I started
with the tarball here: http://autobuilder.yoctoproject.org/nightly/CURRENT

Full transcript.



srifenbark@scottrif-desktop:~$ cd
poky-0b09e50810162a07ef0aecee91ee32b4a36334a3
srifenbark@scottrif-desktop:~/poky-0b09e50810162a07ef0aecee91ee32b4a36334a3$
source oe-init-build-env
You had no conf/local.conf file. This configuration file has therefore been
created for you with some default values. You may wish to edit it to use a
different MACHINE (target hardware) or enable parallel build options to take
advantage of multiple cores for example. See the file for more information
as
common configuration options are commented.

The Yocto Project has extensive documentation about OE including a reference
manual
which can be found at:
http://yoctoproject.org/documentation

For more information about OpenEmbedded see their website:
http://www.openembedded.org/

You had no conf/bblayers.conf file. The configuration file has been created
for
you with some default values. To add additional metadata layers into your
configuration please add entries to this file.

The Yocto Project has extensive documentation about OE including a reference
manual
which can be found at:
http://yoctoproject.org/documentation

For more information about OpenEmbedded see their website:
http://www.openembedded.org/



### Shell environment set up for builds. ###

You can now run 'bitbake <target>'

Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
meta-toolchain-sdk
adt-installer
meta-ide-support

You can also run generated qemu images with a command like 'runqemu qemux86'

srifenbark@scottrif-desktop:~/poky-0b09e50810162a07ef0aecee91ee32b4a36334a3/build$
bitbake -k core-image-sato
Pseudo is not present but is required, building this first before the main
build
Parsing recipes: 100% |#########################################| Time:
00:00:48
Parsing of 825 .bb files complete (0 cached, 825 parsed). 1129 targets, 22
skipped, 0 masked, 0 errors.

Build Configuration:
BB_VERSION = "1.15.3"
TARGET_ARCH = "i586"
TARGET_OS = "linux"
MACHINE = "qemux86"
DISTRO = "poky"
DISTRO_VERSION = "1.2+snapshot-20120927"
TUNE_FEATURES = "m32 i586"
TARGET_FPU = ""
meta
meta-yocto
meta-yocto-bsp = "<unknown>:<unknown>"

NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 63 tasks of which 0 didn't need to be rerun
and all succeeded.
Loading cache: 100% |###########################################| ETA:
00:00:00
Loaded 1130 entries from dependency cache.

Build Configuration:
BB_VERSION = "1.15.3"
TARGET_ARCH = "i586"
TARGET_OS = "linux"
MACHINE = "qemux86"
DISTRO = "poky"
DISTRO_VERSION = "1.2+snapshot-20120927"
TUNE_FEATURES = "m32 i586"
TARGET_FPU = ""
meta
meta-yocto
meta-yocto-bsp = "<unknown>:<unknown>"

NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: validating kernel configuration

WARNING: The recipe is trying to install files into a shared area when those
files already exist. Those files are:

/home/scottrif/poky-0b09e50810162a07ef0aecee91ee32b4a36334a3/build/tmp/sysroots/x86_64-linux/usr/share/sgml/openjade-1.3.2/catalog
WARNING: The recipe is trying to install files into a shared area when those
files already exist. Those files are:

/home/scottrif/poky-0b09e50810162a07ef0aecee91ee32b4a36334a3/build/tmp/sysroots/qemux86/usr/include/python2.7/pyconfig.h

/home/scottrif/poky-0b09e50810162a07ef0aecee91ee32b4a36334a3/build/tmp/sysroots/qemux86/usr/lib/libpython2.7.so

/home/scottrif/poky-0b09e50810162a07ef0aecee91ee32b4a36334a3/build/tmp/sysroots/qemux86/usr/lib/libpython2.7.so.1.0

/home/scottrif/poky-0b09e50810162a07ef0aecee91ee32b4a36334a3/build/tmp/sysroots/qemux86/usr/lib/python2.7/config/Makefile
WARNING: Failed to fetch URL git://git.yoctoproject.org/libowl;protocol=git,
attempting MIRRORS if available
ERROR: Fetcher failure: Fetch command failed with exit code 2, output:

gzip: stdin: invalid compressed data--crc error

gzip: stdin: invalid compressed data--length error
tar: Skipping to next header
tar: Child returned status 1
tar: Error is not recoverable: exiting now

ERROR: Function failed: Fetcher failure for URL:
'git://git.yoctoproject.org/libowl;protocol=git'. Unable to fetch URL from
any source.
ERROR: Logfile of failure stored in:
/home/scottrif/poky-0b09e50810162a07ef0aecee91ee32b4a36334a3/build/tmp/work/i586-poky-linux/libowl-0.1+git1+6ebc8ac8f8575278dd40a535cadefa26374e44b1-r0/temp/log.do_fetch.1973
ERROR: Task 2306
(/home/scottrif/poky-0b09e50810162a07ef0aecee91ee32b4a36334a3/meta/recipes-sato/libowl/libowl_git.bb,
do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 5560 tasks of which 339 didn't need to be
rerun and 1 failed.

Summary: 1 task failed:

/home/scottrif/poky-0b09e50810162a07ef0aecee91ee32b4a36334a3/meta/recipes-sato/libowl/libowl_git.bb,
do_fetch
Summary: There were 3 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
srifenbark@scottrif-desktop:~/poky-0b09e50810162a07ef0aecee91ee32b4a36334a3/build$





Scott Rifenbark

Intel Corporation

Yocto Project Documentation

503.712.2702

503.341.0418 (cell)




_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto

I have recipes for if 3.3 actually I will publish it after 1.3 release it needs some fine touches

Hi all,

Are there any plans for Yocto to include Python 3.2.3 as an alternative to the Python 2.7.3 recipes?  I might need to use it at some point, so I was wondering if it was on the roadmap.

Thanks!
-------------------------------------------------------
Daniel Norris

On Thu, 2012-09-27 at 17:10 +0300, Mihai Lindner wrote:

On 2012-09-27 14:31, Burton, Ross wrote:

Hi,

If I add meta-intel and meta-cedartrail to my bblayers, when I try and
do an atom-pc build (which I thought should still work, right?) I get
the following error:

NOTE: Error during finalise of
/home/ross/Yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.0.bb
ERROR: ExpansionError during parsing
/home/ross/Yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.0.bb:
Failure expanding variable SRCPV, expression was
${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError:
Fetcher failure for URL:
'git://git.yoctoproject.org/linux-yocto-3.0;protocol=git;bareclone=1;branch=yocto/standard/common-pc/atom-pc,meta,yocto/pvr;name=machine,meta,pvr'.
Please set SRCREV to a valid value

That's a bug, right?

Yeah, looks like the other SRC_URIs do that, but it's missing from that
SRC_URI - I just pushed a fix for this one to meta-intel/master.

Tom

Ross
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto

That's a bug alright.
It seems the overall SRC_URI of linux-yocto is overwritten by meta-cedartrail layer, when included. Should be fixed by using SRC_URI_cedartrail instead.

Hi,

I have a recipe that uses GNU autoopts, which generates a dependency on libopts. This is the library that is required for any package using autoopts to compile.

GNU autoopts is a tool that is found embedded in GNU autogen as an example of autogen use, but is also a package in its own right. When you configure and build autogen, you also configure and build autoopts. When you build autoopts, it in turn builds the libopts shared library, static library and source tarball. The tarball is so that it can be used inside your packages source tree, for systems that do not have libopts installed. As far as I can tell via Google, most packages just embed the libopts in their source tree e.g. TCPRELAY and ntp.

As autogen and autoopts are required native packages, If the target package requires libopts, then in this case it finds the libopts.so from native and then at image creation time it complains that the library is not available. To build libopts for the target, you need to either build the whole dependency tree behind autogen, which will build autoopts and the wanted library (with or without bludgeoning autogen's configure script into shape), or share the source tarball during the native building stage for downstream consumers. My first thought was to copy the src tarball to DL_DIR, and have a corresponding target libopts.bb recipe or similar, but as it turns out autogen has a mechanism for this, `autoopts-config libsrc` (as per the libopts tarball README). The tarball is not designed to be configured as a standalone library and plugs into the packages configure - which as you can guess I'm in the process of doing for this package.

So I'm posting this to the list for others who may trip over it, and as a question as to what to do, in the general case where you have something generated by a package in 'native' and you want to share it with a package in 'target'. Rebuild everything? Create a finder script?

Regards,

Tim.

On 2012-09-27 14:31, Burton, Ross wrote:

Hi,

If I add meta-intel and meta-cedartrail to my bblayers, when I try and
do an atom-pc build (which I thought should still work, right?) I get
the following error:

NOTE: Error during finalise of
/home/ross/Yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.0.bb
ERROR: ExpansionError during parsing
/home/ross/Yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.0.bb:
Failure expanding variable SRCPV, expression was
${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError:
Fetcher failure for URL:
'git://git.yoctoproject.org/linux-yocto-3.0;protocol=git;bareclone=1;branch=yocto/standard/common-pc/atom-pc,meta,yocto/pvr;name=machine,meta,pvr'.
Please set SRCREV to a valid value

That's a bug, right?

Ross
_______________________________________________
yocto mailing list
yocto@...
https://lists.yoctoproject.org/listinfo/yocto

That's a bug alright.
It seems the overall SRC_URI of linux-yocto is overwritten by meta-cedartrail layer, when included. Should be fixed by using SRC_URI_cedartrail instead.

--
Mihai Lindner

Hi,

If I add meta-intel and meta-cedartrail to my bblayers, when I try and
do an atom-pc build (which I thought should still work, right?) I get
the following error:

NOTE: Error during finalise of
/home/ross/Yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.0.bb
ERROR: ExpansionError during parsing
/home/ross/Yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.0.bb:
Failure expanding variable SRCPV, expression was
${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError:
Fetcher failure for URL:
'git://git.yoctoproject.org/linux-yocto-3.0;protocol=git;bareclone=1;branch=yocto/standard/common-pc/atom-pc,meta,yocto/pvr;name=machine,meta,pvr'.
Please set SRCREV to a valid value

That's a bug, right?

Ross

I just noticed that the open bug trends don't call out the medium+ bugs. Can these be added?

From: <Serban>, Laurentiu Serban <laurentiu.serban@...<mailto:laurentiu.serban@...>>
Date: Monday, September 24, 2012 2:32 PM
To: "yocto@...<mailto:yocto@...>" <yocto@...<mailto:yocto@...>>
Subject: [yocto] Yocto Bug Trend ww38

Hello,

The Yocto Bug Trend was updated for ww38 https://wiki.yoctoproject.org/wiki/Yocto_Bug_Trend

Br,

Laurentiu Serban
QA Engineer
Open Source Technology Center
System Software Division Romania
Desk: +40 31 8604742
iNET: 88451042

Dear Chris,

In message <CABcZANmPe_D+GPWxnkVZCmE9ti011ZDSXxPix8ztW4vrdYiyZA@...> you wrote:

Well, the comment in "meta-yocto/conf/bblayers.conf.sample" says:

# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly

This suggests that such changes are not exactly unusual. But any such
change will cause the build to fail, because the sanity checker uses a
different value.

This is wrong. A compatibility break in bblayers.conf is *extremely* rare.

If such a change is allowed and is done intentionally, then it should
be considered "sane", and the sanity checker should not complain.

Wrong. The user has to know that they may need to change their
bblayers.conf to match the upstream structure. If it didn't complain,
they could silently break or encounter unexpected behavior.

Sorry, but I don't get how this is supposed to work.

I have an incompatible change, and increase LAYER_CONF_VERSION in my
meta layer's bblayers.conf.sample . When sourcing oe-init-build-env,
this file gets copied to the build dir as conf/bblayers.conf.
Building with this setting fails, because the samity checker does not
accept the value. So I have to actually undo the change I made in
bblayers.conf.sample to make it build.

My internal sanity checker barfs on such logic...

Best regards,

Wolfgang Denk

--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@...
"Tell the truth and run." - Yugoslav proverb

On Wed, Sep 26, 2012 at 11:36 AM, Wolfgang Denk <wd@...> wrote:

By "better way to deal with these", what would you suggest? I don't see any
alternative that avoids the BSP components just disappearing for users who
have existing configurations.

Well, the comment in "meta-yocto/conf/bblayers.conf.sample" says:

# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly

This suggests that such changes are not exactly unusual. But any such
change will cause the build to fail, because the sanity checker uses a
different value.

This is wrong. A compatibility break in bblayers.conf is *extremely* rare.

If such a change is allowed and is done intentionally, then it should
be considered "sane", and the sanity checker should not complain.

Wrong. The user has to know that they may need to change their
bblayers.conf to match the upstream structure. If it didn't complain,
they could silently break or encounter unexpected behavior.

The problem (and the longer I think about it the less I hesitate to
call it a plain bug) is that we allow for meta layer specific values
of LAYER_CONF_VERSION, while still assuming a single hard-coded
value in meta/conf/sanity.conf could be used as reference.

This _cannot_ work.

But when I'm supposed to overwrite the setting (to match the sanity
checker's expectations) in my local conf/bblayers.conf, then why do we
bother to set a dieferent value in the meta layer in the first place?
And hey, why do we check this value at all if all we can do is always
make it match manually?

Not everyone using oe-core (meta) also uses meta-yocto. Only those
using the latter were affected by this particular upstream structure
change.

I understand the intention, but the current implementation is just
broken, and I don't see a way to fix it. It would probably be better
to remove this test than to leave it as is.

Again, that'd leave the user with a bblayers.conf that may no longer
do what they intended it to do. Better to fail than potentially build
in ways not matching the user's previous expectations.
--
Christopher Larson

Dear Paul,

In message <224780988.1nyHnvScgz@helios> you wrote:

If meta layer specific values of LAYER_CONF_VERSION are allowed, the
sanity checker needs a better way to deal with these; alternatively,
above setting in meta-yocto/conf/distro/poky.conf is wrong. So either
of these should be fixed.

By "better way to deal with these", what would you suggest? I don't see any
alternative that avoids the BSP components just disappearing for users who
have existing configurations.

Well, the comment in "meta-yocto/conf/bblayers.conf.sample" says:

# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly

This suggests that such changes are not exactly unusual. But any such
change will cause the build to fail, because the sanity checker uses a
different value.

If such a change is allowed and is done intentionally, then it should
be considered "sane", and the sanity checker should not complain.

The problem (and the longer I think about it the less I hesitate to
call it a plain bug) is that we allow for meta layer specific values
of LAYER_CONF_VERSION, while still assuming a single hard-coded
value in meta/conf/sanity.conf could be used as reference.

This _cannot_ work.

But when I'm supposed to overwrite the setting (to match the sanity
checker's expectations) in my local conf/bblayers.conf, then why do we
bother to set a dieferent value in the meta layer in the first place?
And hey, why do we check this value at all if all we can do is always
make it match manually?

I understand the intention, but the current implementation is just
broken, and I don't see a way to fix it. It would probably be better
to remove this test than to leave it as is.

Best regards,

Wolfgang Denk

--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@...
If a packet hits a pocket on a socket on a port,
And the bus is interrupted as a very last resort,
And the address of the memory makes your floppy disk abort,
Then the socket packet pocket has an error to report! - Ken Burchill?