Aníbal Limón [Tue, 2 Feb 2016 23:08:56 +0000 (17:08 -0600)]
oeqa/oetest: Fix compatibility SDK tests using eSDK.
When run SDK tests over eSDK we need to use SDKExtTestContext
instead of SDKTestContext because if we use SDKTestContext search
for SDK manifest and depends on the SDK manifest generation so
populate_sdk needs to be executed.
Adds a compatibility mode flag to SDKExtTestContext for search tests
over sdk module instead of sdkext module and change testsdk calls
to comply with this new param.
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Aníbal Limón [Sun, 31 Jan 2016 14:45:47 +0000 (08:45 -0600)]
testsdkext: Add skeleton for support Extensible SDK tests.
oeqa/sdkext: Add module and __init__.py will contain eSDK tests.
classes/testsdk: Add support for run eSDK tests.
oeqa/oetest: Create oeSDKExtTest for now only inherit oeSDKTest,
modified SDKExtTestContext now inherit SDKTestContext
and set sdkext filesdir for store data fixtures.
Signed-off-by: Aníbal Limón <limon.anibal@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Aníbal Limón [Thu, 4 Feb 2016 22:14:26 +0000 (16:14 -0600)]
oeqa/oetest: oeSDKTest when run a command redirect env output to null
Some tests are failing because the eSDK env load script shows a help
message on the output so redirect this to /dev/null.
There was a discussion with Paul Eggleton [1], he don't want to have env
variables to change the behaviour of what the env script needs to print
so redirect the output in oeSDK.run() method. I didn't agree because
it can hides another messages like error ones and with the variable you
can control what prints or not.
Aníbal Limón [Sat, 30 Jan 2016 17:05:15 +0000 (11:05 -0600)]
testimage/testsdk: Modularize TestContext.
Move anonymous duplicated class TestContext from testimage/testsdk to
oeqa/oetest now we have two new classes ImageTestContext and
SDKTestContext with common code in TestContext class.
Signed-off-by: Aníbal Limón <limon.anibal@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Aníbal Limón [Thu, 28 Jan 2016 16:09:02 +0000 (10:09 -0600)]
classes/testsdk: Add new class testsdk.
Moves all the testsdk code from testimage in order to have it's own
class because new tests will be added for extensible SDK.
The old paths for store logs "${WORKDIR}/testimage" and sdk
"${WORKDIR}/testimage-sdk" was maintained for compatibility may be
change to point testsdk after review the codebase.
The dependency of QEMU was removed because isn't needed.
Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Ed Bartosh [Wed, 10 Feb 2016 08:09:37 +0000 (10:09 +0200)]
oeqa: setup bitbake logger after tinfoil.shutdown
Bitbake logger stops working after tinfoil.shutdown removes console
handler from it. This makes bb.{error,warn,note,critical} messages
disappear from the console. Adding console handler to bitbake logger
again should fix this issue.
Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Armin Kuster [Sun, 31 Jan 2016 19:55:30 +0000 (11:55 -0800)]
glibc-locale: fix QA warning
WARNING: QA Issue: glibc-locale: /glibc-binary-localedata-sd-in/usr/lib/locale/sd_IN/LC_CTYPE is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
fix type Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Sun, 7 Feb 2016 17:10:43 +0000 (17:10 +0000)]
sstatetests: Fix after change to sstate populate_lic SWSPEC
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=9fd214d2e7a931cfb46f40cb76d49aeb07af612e
changed SSTATE_SWSPEC, correctly however it did mean that some sstate files
now appear where the tests don't expect them. Filter the test results
to ignore the correct behaviour.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Andre McCurdy [Fri, 5 Feb 2016 21:34:52 +0000 (13:34 -0800)]
gstreamer1.0: avoid including <sys/poll.h> directly
musl libc generates warnings if <sys/poll.h> is included directly.
The warnings only cause problems for the git versions (-Werror is
turned off for GStreamer stable releases), but since <sys/poll.h> can
be conviently disabled via configure let's avoid it for all versions.
Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Andre McCurdy [Fri, 5 Feb 2016 19:56:19 +0000 (11:56 -0800)]
gmp_4.2.1: fix build for MIPS
The h asm constrain (to extract the high part of a multiplication
result) has not been recognised since gcc 4.4:
https://gcc.gnu.org/gcc-4.4/changes.html
Drop the MIPS umul_ppmm() implementations which rely on "=h" and fall
back to the older implementations (which use explicit mfhi and mflo
instructions to move the high and low parts of the multiplication
result into their destinations).
Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Andre McCurdy [Fri, 5 Feb 2016 19:56:17 +0000 (11:56 -0800)]
gmp: move BBCLASSEXTEND = "native nativesdk" from gmp.inc into 6.1.0 recipe
It's unlikely that native builds of gmp 4.2.1 (ie the last LGPLv2
version) would ever be required (and given that recent versions of gcc
require gmp >= 4.3.2, native builds of gmp 4.2.1 are unlikely to work
very well). Restrict native and nativesdk builds to gmp 6.1.0 only.
https://gcc.gnu.org/install/prerequisites.html
Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Andre McCurdy [Fri, 5 Feb 2016 19:56:16 +0000 (11:56 -0800)]
gmp: move SRC_URI out of gmp.inc + minor reformatting
The base SRC_URI in gmp.inc was wrong for gmp 4.2.1 and was not being
used by gmp 6.1.0. Remove it and make each recipe responsible for
defining its own SRC_URI.
Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Drew Moseley [Fri, 5 Feb 2016 17:56:20 +0000 (10:56 -0700)]
image_types.bbclass: Embed IMAGE_NAME in ubinize config file
When using the FSTYPE multiubi, make sure that each image build
has a unique config file. Without this there is a race condition
when building multiple images in a single bitbake command which
results in errors similar to:
ERROR: Error: The image creation script
'blah/tmp/work/blah/core-image-base/1.0-r0/temp/create_image.multiubi' returned 1:
iniparser: cannot open ubinize_normal.cfg
ubinize: error!: cannot load the input ini file "ubinize_normal.cfg"
mv: cannot stat 'ubinize_normal.cfg': No such file or directory
WARNING: blah/tmp/work/blah/core-image-base/1.0-r0/temp/create_image.multiubi:1 exit 1 from
mv ubinize${vname}.cfg blahtmp/deploy/images/blah/
Signed-off-by: Drew Moseley <drew_moseley@mentor.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Khem Raj [Fri, 5 Feb 2016 16:52:41 +0000 (16:52 +0000)]
security_flags: use -fstack-protector-strong
This is a better version of -fstack-protector-all with reduced stack usage and
better performance yet giving same amount of coverage. It's available in gcc
4.9 onwards.
https://outflux.net/blog/archives/2014/01/27/fstack-protector-strong/ has more
details.
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Khem Raj [Tue, 2 Feb 2016 18:32:49 +0000 (10:32 -0800)]
gcc: Fix build on musl with -fstack-protector
When enabling the secutity flags on musl based targets the builds fail
due to libssp(gcc-runtime) build asking to link with libssp and
libssp_nonshared.a when configuring libssp itself. This does not work
with musl since it does provide ssp implementation but not like glibc
where these libraries are separate to libc
Fix the nios2 patch with upstream status while at it and generate the
patch after applying to my tree
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Take `pwd` to be <initial-dir>. The %s path is relative to it. The value
of %s is "output_folder/build". The current code works as follows:
Changing directory to %s and finding the sources (after cd'ing) to cpio
with output redirection to %s/initrd.cpio triggers the following error
"Error: exec_cmd: cd output_folder/build/INITRD && find . | cpio -o -H
newc >output_folder/build/initrd.cpio returned '1' instead of 0"
This happens because after the cd, `pwd` is <initial-dir>/%s and by the
redirect we write the result to to <initial-dir>/%s/%s/initrd.cpio which
obviously does not exist.
Fix this by getting the sources with "find %s" instead of "cd && find ."
Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Ross Burton [Fri, 5 Feb 2016 11:44:00 +0000 (11:44 +0000)]
libpcre: enable unicode properties by default
Enable Unicode properties by default, as they're useful and for example GLib
needs them. As there is an impact to code size add this as a PACKAGECONFIG so
tightly constrained environments can save space by potentially disabling them.
Also change --enable-utf8 to --enable-utf, as the former is a compatibility
option for the latter.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Ross Burton [Fri, 5 Feb 2016 09:45:24 +0000 (09:45 +0000)]
python3: remove optimize by default patch
Python 3 resurrected the default to optimised patch, on the rationale that
embedded systems want all the performance they can get. Unfortunately the only
impact Python "optimisation" has is to remove all asserts which can be actively
harmful, so remove this patch.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Ross Burton [Thu, 4 Feb 2016 13:02:25 +0000 (13:02 +0000)]
security_flags.inc: don't do -pie for syslinux
sysroots/x86_64-linux/usr/libexec/x86_64-poky-linux/gcc/x86_64-poky-linux/5.3.0/ld:
syslinux.o: relocation R_X86_64_32 against `.rodata.str1.1' can not be used
when making a shared object; recompile with -fPIC
Signed-off-by: Ross Burton <ross.burton@intel.com>
Andre McCurdy [Thu, 4 Feb 2016 00:30:33 +0000 (16:30 -0800)]
neon: convert to PACKAGECONFIG
Along with the conversion to PACKAGECONFIG, drop unnecessary
dependencies on time (it's an app, not a library?) and libxml2 (neon
requires either expat or libxml2 for xml parsing, defaulting to expat
if both are available).
Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Jens Rehsack [Fri, 5 Feb 2016 10:25:40 +0000 (11:25 +0100)]
cross-localedef-native: add ABI breaking glibc patch
Add patch from commit 96b1b5c127e9e0e637aaf7948cf3330a94a5cd57 to cross-localedef-native
to avoid broken images built with ENABLE_BINARY_LOCALE_GENERATION set to 1:
$ sh -c "export LANG=de_DE; ls -la"
sh: loadlocale.c:130: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_COLLATE) / sizeof (_nl_value_type_LC_COLLATE[0]))' failed.
Aborted
Signed-off-by: Jens Rehsack <sno@netbsd.org> Signed-off-by: Ross Burton <ross.burton@intel.com>
Richard Purdie [Thu, 4 Feb 2016 08:31:38 +0000 (08:31 +0000)]
uninative: Improve error handling
We need to improve the error handling here, things were breaking and
yet the user wasn't seeing the issues. We need to skip libraries as
we process the files.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Ross Burton <ross.burton@intel.com>
Richard Purdie [Thu, 4 Feb 2016 08:31:07 +0000 (08:31 +0000)]
patchelf: Add patch to handle large files
There were "maximum size exceeded" errors from patchelf when processing
qemu-native. There is an issue open for this upstream, add a patch
proposed there for this issue. "32" was increased to "64" to handle our
qemu-ppc binary.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Ross Burton <ross.burton@intel.com>
This if branch is causing the following error during do_rootfs:
"Exception: UnboundLocalError: local variable 'cfg_file' referenced
before assignment". This happends because the cfg_file variable is
defined at a deeper nesting level (just above the if branch).
Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Randy Witt [Thu, 4 Feb 2016 20:31:44 +0000 (12:31 -0800)]
populate_sdk_ext: Add support for a "minimal" type
If the user sets the SDK_EXT_TYPE variable to "minimal" then the sdk won't
contain any sstate. The sstate can come from an sstate mirror and be
installed on demand as usual.
Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Randy Witt [Thu, 4 Feb 2016 20:31:42 +0000 (12:31 -0800)]
toolchain-scripts.bbclass: Use PYTHONPATH instead of PYTHONHOME
In the extensible sdk it was originally intended that the native sstate
would always be setscened as part of the sdk installation. However, the
soon to come "minimal" sdk won't do that.
A side effect of that is that pointing PYTHONHOME at the native sysroot
within the "bitbake workspace" won't work. For now only set PYTHONPATH
instead and continue using the python that comes from buildtools.
Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Randy Witt [Thu, 4 Feb 2016 20:31:41 +0000 (12:31 -0800)]
copy_buildsystem.py: Pass the nativelsb argument to gen-lockedsig-cache
If the nativelsb argument is not used, then create_locked_sstate_cache()
can get collisions when moving the files from the input_sstate_cache
to the output_sstate_cache.
The specific case where this was encountered was when a "universal"
nativelsb directory already existed in the input_sstate_cache.
Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ross Burton [Fri, 5 Feb 2016 20:50:34 +0000 (20:50 +0000)]
gtk-theme-torturer: remove from oe-core
This recipe is very old, unmaintained, not used at all in OE-Core, and not
useful in a world that has moved to GTK+ 3 (even if Sato is slow at catching
up).
Signed-off-by: Ross Burton <ross.burton@intel.com>
Richard Purdie [Sat, 6 Feb 2016 12:30:02 +0000 (12:30 +0000)]
bitbake.conf/native/nativesdk: Set PKG_CONFIG_SYSTEM_ at top level
Setting PKG_CONFIG_SYSTEM_{HEADERS/INCLUDE}_PATH for nativesdk isn't
enough, we also need to deal with multlib cases where libdir from
pkg-config-native isn't correct. Native builds are about the only
case where this variable shouldn't be set.
Therefore move the code from nativesdk to bitbake.conf and unexport it
in the native case.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ross Burton [Thu, 4 Feb 2016 16:29:53 +0000 (16:29 +0000)]
pango: unset LDFLAGS when building gen_all_unicode
When building the native gen_all_unicode binary we need to also unset LDFLAGS as
otherwise the *target* LDFLAGS will be used. At best the options are harmless
but if there are options that the host compiler doesn't support then the compile
will fail. For example, if the host gcc is version 4.8 but LDFLAGS contains
-fstack-protector-strong which in 4.9 onwards.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Richard Purdie [Fri, 5 Feb 2016 10:51:32 +0000 (10:51 +0000)]
nativesdk: Set PKG_CONFIG_SYSTEM_ variables
When building nativesdk recipes, we noticed paths going into .pc files
which should have been suppressed since these were standard library
search paths. pkgconfig-native sets these variables to sane values
for native recipes, we need it set to values for our specific library
paths in the nativesdk case.
Setting these values cleans up the .pc files and suppresses the paths.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Khem Raj [Fri, 22 Jan 2016 20:45:03 +0000 (20:45 +0000)]
local.conf.sample.extended: Document HOW-TO enable systemd or busbox for init system
OE core provides systemd,busybox as options for system init system along
with sysvinit being the default. Document the needed settings to enable
systemd and busybox as options if user wishes.
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Thu, 4 Feb 2016 12:38:50 +0000 (12:38 +0000)]
insane: Fix populate_sysroot sanity test path
This was correct for native/cross paths but not for target ones which
meant the tests weren't running in some cases. Fix the path to be
correct in both cases.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Andre McCurdy [Wed, 3 Feb 2016 21:17:11 +0000 (13:17 -0800)]
gnutls: update 3.4.8 -> 3.4.9
This version fixes bugs in the current stable branch.
* Version 3.4.9 (released 2016-02-03)
** libgnutls: Corrected ALPN protocol negotiation. Before GnuTLS would
negotiate the last commonly supported protocol, rather than the
first. Reported by Remi Denis-Courmont (#63).
** libgnutls: Tolerate empty DN fields in informational output
functions.
** libgnutls: Corrected regression causes by incorrect fix in
gnutls_x509_ext_export_key_usage() at 3.4.8 release.
** API and ABI modifications:
No changes since last version.
Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Maxin B. John [Wed, 3 Feb 2016 14:47:40 +0000 (16:47 +0200)]
linux-firmware: update to latest revision 52442afee
- Update to latest linux-firmware
- Renamed qat_dh895xcc_firmware to qat_firmware based on commit 8d1f7a11
- Updated license info for the ath9k_htc firmware
Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Ross Burton [Wed, 3 Feb 2016 16:34:52 +0000 (16:34 +0000)]
license.bbclass: add LICENSE_CREATE_PACKAGE to perform_packagecopy vardeps
This class has a perform_packagecopy_prepend() that uses LICENSE_CREATE_PACKAGE,
but the BitBake variable dependency code doesn't know that oe.data.typed_value()
is a getter. Until BitBake knows this, add an explicit vardeps.
[ YOCTO #5635 ]
Signed-off-by: Ross Burton <ross.burton@intel.com>
That commit completely breaks KBUILD_DEFCONFIG because it relies on
$ARCH to match between the target OE arch and the kernel subdirectory
containing the defconfigs. In the kernel all defconfigs for everything
x86-based (including x86_64) is stored in dir arch/x86/configs/
kernel-yocto.bbclass correctly searches for all the defconfigs inside
${S}/arch/${ARCH}/configs/${KBUILD_DEFCONFIG}
Commit 8d310b249 makes it search in wrong places and _only_ if you
define TARGET_ARCH = "athlon" will it search x86 which is nonsensical.
The commit further adds an if clause to hack the mungled kernel arches
back to their original values (ugh) in do_shared_workdir which is run
after do compile, but of course the build breaks before that in
do_kernel_metadata because of the KBUILD_DEFCONFIG mentioned above (so
that hack is useless).
Please fix that corner case bug in another way which does not completely
screw up the kernel arch mapping & defconfig logic. If 64bit configs are
generated in the kernel for 32bit machines because the host is asked,
then it it a bug in the kernel, it is of no use to hack around it in OE.
Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
changed util-linux priority to match busybox (50) which means sometimes
one and sometimes the other wins in image installs. We want util-linux to
win compared to busybox.
The old level (100) does conflict with other utils so pick 80 as a
good intermediate value.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Andre McCurdy [Tue, 2 Feb 2016 21:59:35 +0000 (13:59 -0800)]
libxsettings-client: drop obsolete disable_Os_option.patch
This patch to configure.ac to change the default CFLAGS from -Os to
-O2 was added in 2010 as a workaround for a ppc specific bug which
affected gcc 4.5.x:
Maciej Borzecki [Tue, 2 Feb 2016 15:15:20 +0000 (16:15 +0100)]
wic: default to empty bootloader config
A kickstart file for non-x86 boards may have no 'bootloader' stanza. It
is the usual case if bootloader is setup using other mechanism than
through wic, and is for instance a part of u-boot configuration. In such
case the 'bootloader' field in the KickStart class will be
uninitialized. Instead of adding an empty bootloader line in every
kickstart file call the bootloader parser with empty argument list to
get defaults namespace.
Signed-off-by: Maciej Borzecki <maciej.borzecki@open-rnd.pl> Signed-off-by: Ross Burton <ross.burton@intel.com>
Chen Qi [Wed, 3 Feb 2016 07:50:21 +0000 (15:50 +0800)]
copy_buildsystem: add ability to exclude layers
In some cases, we may have some kind of download layers in BBLAYERS, so
that we can set BB_NO_NETWORK to "1". This results in extremely large
extensible SDK. And we actually don't need these download layers in the
SDK.
Add a new variable, SDK_LAYERS_EXCLUDE, to enable users to explicitly
exclude some layers when generating the extensible SDK.
[YOCTO #8878]
Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Elliot Smith [Tue, 2 Feb 2016 10:25:03 +0000 (10:25 +0000)]
toaster.bbclass: reinstate scan for artifacts in the sdk directory
During refactoring of the SDK/artifact scan code in toaster.bbclass,
the code to find other non-image artifacts in the images/ directory
was incorrectly removed.
Reinstate that code and clean it up so it's clearer what's happening
and so that non-image artifacts are correctly reported.
[YOCTO #8956]
Signed-off-by: Elliot Smith <elliot.smith@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Elliot Smith [Tue, 2 Feb 2016 10:25:02 +0000 (10:25 +0000)]
toaster.bbclass: attach image file scan postfunc to do_image_complete
The postfunc for finding image files after completion of a build
fails, as the image files we're interested in don't exist at the
point when the scan is currently done (following do_rootfs).
Attach the postfunc for scanning for image files to the new
do_image_complete task, which definitely runs after the image files
have been created.
[YOCTO #8956]
Signed-off-by: Elliot Smith <elliot.smith@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ross Burton [Mon, 25 Jan 2016 13:38:00 +0000 (13:38 +0000)]
meta: add ASSUME_PROVIDED dependency on wget-native for http fetches
For clarity and consistency, add a dependency on wget-native for any URIs that
will be fetched using the wget fetcher, and add wget-native to ASSUME_PROVIDED.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Richard Purdie [Tue, 2 Feb 2016 13:53:13 +0000 (13:53 +0000)]
sstate: Fix SSTATE_SWSPEC only used by populate_lic tasks
This variable is only used by populate_lic tasks (gcc-source overrides it)
and refers to BPN. In recipes like gcc, where there are multiple variants,
it is resulting in sstate objects which encode PN (they install into a PN subdir)
but the sstate object reflects BPN. This leads to corruption between then and
eventually, warnings from image builds like:
WARNING: The license listed GPLv3 was not in the licenses collected for recipe gcc
WARNING: The license listed GPL-3.0-with-GCC-exception was not in the licenses collected for recipe gcc
WARNING: The license listed GPLv3 was not in the licenses collected for recipe gcc
WARNING: The license listed NCSA was not in the licenses collected for recipe gcc-sanitizers
WARNING: The license listed MIT was not in the licenses collected for recipe gcc-sanitizers
WARNING: The license listed GPL-3.0-with-GCC-exception was not in the licenses collected for recipe gcc
WARNING: The license listed GPLv3 was not in the licenses collected for recipe gcc
WARNING: The license listed NCSA was not in the licenses collected for recipe gcc-sanitizers
By referring to PN, as used by license.bbclass, this issue is resolved.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Tue, 2 Feb 2016 13:52:38 +0000 (13:52 +0000)]
package.bbclass: Add data expansion to do_split_packages()
do_split_packages is often called with parameters which need expansion.
This happens to work at the moment since python functions are expanded
before execution but likely will not happen in future and isn't good
code practise.
Expand the common parameters do_split_packages() to avoid regressions.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Richard Purdie [Tue, 2 Feb 2016 13:50:47 +0000 (13:50 +0000)]
busybox/gtk/perl/base-passwd: Ensure data is correctly expanded
Where variables are used in python, we need to ensure they are expanded.
This happens to work at the moment but likely will not happen in future
and isn't good code practise.
Its mostly an issue around key values, since bitbake has already
performed key expansion when these functions are executed.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
