Fixed
Created: Aug 13, 2015
Updated: Dec 3, 2018
Resolved Date: Aug 20, 2015
Found In Version: 6.0.0.21
Fix Version: 6.0.0.24
Severity: Standard
Applicable for: Wind River Linux 6
Component/s: Build & Config
Host OS: Linux 64
Architecture: IA64
The subject error happens when the –with-layer option is used to pass in custom layers. This has never been a problem before, but something specific to this path name is causing the error seen below.
If you move:
/nov_integration/100.15.1.57/linux/wrlinux
to just:
/local/linux/wrlinux
The workspace configures without any issues, so it doesn’t seem to be specific to anything in the custom layer. If you use the /local/builders path without the –with-layer option then it also configures without issue.
So it seems specific to the path and –with-layer processing.
-------
Generating bitbake config
Substituting scripts and Makefiles
config.status.in is NEWER, copy and re-exec
Updating: /nov_integration/100.15.1.57/linux/wrlinux/Makefile
Updating: /nov_integration/100.15.1.57/linux/wrlinux/scripts/fakestart.sh
Updating: /nov_integration/100.15.1.57/linux/wrlinux/scripts/user-nfs.sh
Updating: /nov_integration/100.15.1.57/linux/wrlinux/scripts/wrl-env-internal
Updating: /nov_integration/100.15.1.57/linux/wrlinux/scripts/wrl-env-setup.mk
Updating: /nov_integration/100.15.1.57/linux/wrlinux/scripts/autoconf.mk
Updating: /nov_integration/100.15.1.57/linux/wrlinux/scripts/quiltPatterns.txt
Updating: /nov_integration/100.15.1.57/linux/wrlinux/scripts/export-layer.sh
Updating: /nov_integration/100.15.1.57/linux/wrlinux/build/Makefile
Updating: /nov_integration/100.15.1.57/linux/wrlinux/build-tools/Makefile
Generating wrlinux compatibility config
ERROR: Execution of event handler 'base_eventhandler' failed
Traceback (most recent call last):
File "base_eventhandler(e)", line 5, in base_eventhandler(e=<bb.event.ConfigParsed object at 0x2865250>)
File "base.bbclass", line 87, in preferred_ml_updates(d=<bb.data_smart.DataSmart object at 0x23b5390>)
UnboundLocalError: local variable 'newval' referenced before assignment
Setting up host-cross and links
Setting up packages link
Creating export directory
Creating project properties
NOTE: Sanity check: Compiler args OK for x86-64.
NOTE: Sanity check: Compiler args OK for x86.
NOTE: Started PRServer with DBfile: /nov_integration/100.15.1.57/linux/wrlinux/bitbake_build/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 35442, PID: 14081
ERROR: Unable to parse /nov_integration/100.15.1.57/linux/wrlinux/layers/oe-core/meta/recipes-core/packagegroups/packagegroup-core-boot.bb: Exited with "1" | ETA: 00:00:58
ERROR: Please ensure that your setting of VIRTUAL-RUNTIME_init_manager (sysvinit) matches the entries enabled in DISTRO_FEATURES
Summary: There were 3 ERROR messages shown, returning a non-zero exit code.
Initial bitbake parse/config failed, moving bitbake_build/conf/local.conf to
bitbake_build/conf/local.conf.failed, in case you want to manually debug.
Please correct your configure settings and try again.
--enable-board=intel-x86-64 --enable-kernel=standard --enable-rootfs=glibc_small --enable-bootimage=cpio.gz --enable-rm-work=yes --enable-rm-oldimgs=yes --with-layer=/nov_integration/100.15.1.57/linux/my_layer --with-template=feature/build_libc --with-rcpl-version=0021
The WRL6 proj_dir is created under:
/nov_integration/100.15.1.57/linux/wrlinux
Custom layers have been created outside the proj_dir:
/nov_integration/100.15.1.57/linux/my_layer
For some reason this particular path is causing an error in the configure script. For example, if you change the proj_dir path to:
/nov_integration/100.15.1.57/linux/wrlinux2
or
/nov_integration/100.15.1.57/linux/wrlnx
it will configure without error. It is only when the proj_dir is configured under:
/nov_integration/100.15.1.57/linux/wrlinux
that is fails. This is reproducible on almost any machine. If you don't specify the --with-layer option then the configure works fine for:
/nov_integration/100.15.1.57/linux/wrlinux
Tried changing the location of my_layer and it still failed so it's not the location of the layers, but the combination of that specific path and the --with-layer option.
