summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFiles
2017-12-21image_types_wic.bbclass: Ensure '-c image_wic' worksOtavio Salvador1
The 'wic' image may use files which has been deployed (e.g in do_deploy) for some partitions that may need to be copied in a specific partition or filesystem (e.g a bootloader). When using 'bitbake <image> -c image_wic', from a clean build, the contents of do_deploy must also be available so we need to ensure all do_deploy of the image dependencies has been complete. Reported-by: Fabio Berton <fabio.berton@ossystems.com.br> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-20rm_work: Handle race with -inital tasksRichard Purdie1
There is a race with rm_work when tasks run deltask do_build since do_rm_work becomes a floating task. Handle this by injecting the populate_sysroot/lic dependencies manually if the tasks returned are empty. This depends on a change to fix bb.build.preceedtask() in bitbake too. [YOCTO #12365] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-20gcc: Drop 6.4Richard Purdie60
We've had 7.x around for long enough now that it should be tested and usable everywhere, drop 6.4. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-20oeqa/selftest/buildoptions: Add test for fortran compiler buildingRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-20oeqa/selftest/archiver: Add test for srpm archiver mode dependenciesRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-20libgfortran: Fix breakage from libbacktrace dependencyRichard Purdie1
In 6.x and 7.x gcc, libgfortran now needs libbacktrace. Enable building of this so that libgfortran builds correctly. [YOCTO #12394] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-20depmodwrapper-cross: Set PACKAGES=''Richard Purdie1
This recipe inherits nopackages but has a non-empty PACKAGES which confuses the archiver class when: INHERIT += "archiver" ARCHIVER_MODE[srpm] = "1" Ensuring PACKAGES is empty removes the errors that occur in this configuration. [YOCTO #11121] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-18image.bbclass: Add additional bb.debug to help track 12304Saul Wold1
We actually caught the ext4 size issue in the wild with the debug output in the oe_mkext234fs() code, but it did not help. What that showed was that the get_rootfs_size was returning a default size of 8192, where as the actual rootfs was more like 10572, thus too large to fit in the created sparse file. This additional temporary debug code should help us determine where the failure might be. More debug for [YOCTO #12304] Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18meta-selftest: wic: Add test for --use-uuid / --fsuuidTom Rini2
- Mount a '/media' partition to wic-image-minimal.wks with a known UUID. - In test_qemu, sort our output from checking the output of 'mount' as it may not be stable. Also, do not check the exit code as passing any output to cut ensures a 0 exit code. - Check for a 'UUID=' line in /etc/fstab with out expected output. Signed-off-by: Tom Rini <trini@konsulko.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18wic: Introduce --fsuuid and have --use-uuid make use of UUID tooTom Rini6
First, allow for wic to be given a filesystem UUID to be used when creating a filesystem. When not provided, wic will generate the UUID to be used. Next, when --use-uuid is passed, we update the fstab to mount things via UUID (and if not found, then use PARTUUID) as UUID is more portable. Signed-off-by: Tom Rini <trini@konsulko.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18wic: partition.py: Update comments slightlyTom Rini1
First, we support squashfs as root, so mention that. Second, the btrfs rootfs creation function had a copy/paste of the previous function comment, remove the irrelevant line. Signed-off-by: Tom Rini <trini@konsulko.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18wic: kparser.py: Check for SquashFS and use-uuidTom Rini1
The SquashFS filesystem does not support UUIDs so make this combination be an error. Signed-off-by: Tom Rini <trini@konsulko.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18image_types: btrfs use sparse file creationSaul Wold1
This will speed up file creation and still allow the btrfs tools to create a full btrfs image. This is similar to what we do for ext234 FS types. Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18maintainers.inc: add an entry for pkgconfAlexander Kanavin1
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2017-12-18maintainers.inc: add an entry for dwarfsrcfilesAlexander Kanavin1
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2017-12-18devtool: add license checksum change handling to 'devtool upgrade'Alexander Kanavin1
Specifically, 'devtool upgrade' will now do these things: 1) determine if any of the license checksums need updating; if so, write the new checksums into the LIC_FILES_CHKSUM value in the recipe that is written to the workspace; 2) print a notice to the standard output: NOTE: New recipe is /home/ak/development/poky/build/workspace/recipes/puzzles/puzzles_git.bb NOTE: License checksums have been updated in the new recipe; please refer to it for the difference between the old and the new license texts. 3) and the cool part: devtool will create a diff of the old and new licenses, and write the diff into the workspace recipe as a comment, like this: ====== FIXME: the LIC_FILES_CHKSUM values have been updated by 'devtool upgrade'. The following is the difference between the old and the new license text. Please update the LICENSE value if needed, and summarize the changes in the commit message via 'License-checksum-change:' tag. (example: 'License-checksum-change: copyright years updated.') The changes: --- LICENCE +++ LICENCE @@ -1,8 +1,9 @@ This software is copyright (c) 2004-2014 Simon Tatham. Portions copyright Richard Boulton, James Harvey, Mike Pinna, Jonas -Klker, Dariusz Olszewski, Michael Schierl, Lambros Lambrou, Bernd -Schmidt, Steffen Bauer, Lennard Sprong and Rogier Goossens. +Kölker, Dariusz Olszewski, Michael Schierl, Lambros Lambrou, Bernd +Schmidt, Steffen Bauer, Lennard Sprong, Rogier Goossens and Michael +Quevillon. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files ====== Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2017-12-18devtool: provide useful defaults for version/commit when upgrading recipesAlexander Kanavin1
Specifically, 'devtool upgrade' will use the latest upstream release if available or latest commit if upstream never makes releases. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2017-12-18devtool: add a 'latest-version' commandAlexander Kanavin1
This command queries the upstream server for what the latest release is and prints the output; it is a much neater way to find out these things than fumbling with distrodata, 'bitbake -c checkpkg' and awkward to read csv output in a file. Examples: python3 (tarballs): NOTE: Current version: 3.5.3 NOTE: Latest version: 3.6.3 rpm (git): NOTE: Current version: 4.13.90 NOTE: Latest version: 4.14.0 NOTE: Latest version's commit: da3720f62e57648fb1dc2a632744d38866139971 puzzles (git without version tags): NOTE: Latest commit: ee8ea9b9785964694cb2b3ad77c3fb2460f49510 Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2017-12-18swig: add patch to support Node.js 7+Paul Eggleton2
Add a patch which has been submitted upstream to support producing bindings for Node.js 7+. This is important to enable mraa to build with newer Node.js versions. Fixes [YOCTO #12293]. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18dbus-test: upgrade to 1.12.2Chen Qi1
Upgrade dbus-test to 1.12.2 as dbus has been upgraded to this version. Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18dbus: upgrade to 1.12.2Chen Qi2
1. os-test.patch is removed because current dbus has removed distro specific init script. 2. Add autoconf-archive to DEPENDS to fix do_configure failure as below. error: Unexpanded AX_ macro found. 3. Modify FILES variable to fix installed-vs-shipped QA issue. Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18conf/machine/include/microblaze: Add MicroBlaze architecture includesNathan Rossi4
Add architecture and tune includes for MicroBlaze. This covers architecture configuration as well as tune configuration and features. The Xilinx MicroBlaze architecture is a soft-core CPU architecture designed for implementation on Xilinx FPGAs. Because the CPU is a soft-core it can be configured differently depending on resource and performance constraints which affect the ABI and supported instructions. The architecture is also used in other Xilinx products where the core is implemented as part of fixed silicon (e.g. Xilinx ZynqMP). The default tune include 'tune-microblaze.inc' provides the baseline (no features enabled) tune configuration for a target machine. This is similar to other architectures such that the machine.conf includes a tune-*.inc. However due to the customizability configuration is specifically handled on a per machine basis. A machine should configure the available tune features by setting the available features directly by appending to the 'TUNE_FEATURES_tune-microblaze' variable. This tune configuration approach is preferred to avoid the definition of an otherwise large set of possible tune configurations for the available features (14 CPU versions and 11 feature configurations), which would otherwise require >1024 predefined tune configurations. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18packagegroup-core-tools-testapps: kexec does not support MicroBlazeNathan Rossi1
The kexec-tools do not currently support MicroBlaze, override the KEXECTOOLS variable to disable the inclusion of these tools in the packagegroup. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18packagegroup-core-sdk: Disable SANITIZERS for MicroBlazeNathan Rossi1
The libasan and libubsan sanitizers are not available for MicroBlaze. Follow the overriding of the SANITIZERS variable as done for other architectures to remove these from the packagegroup when targeting MicroBlaze. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18systemd: fix segfault when terminating systemd --testJoe Slater3
Currently, if "systemd --test" is not allowed to complete sending output, it will segfault. Signed-off-by: Joe Slater <jslater@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18recipetool: create: fix conflict between SRCREV and tagChang Rebecca Swee Fun1
If you specify 'tag=' for a git URL and passed to recipetool create, you will get into Bitbake expansion error shown below: ----- snip ----- $ devtool add --version 2.4.2 mbedtls "git://github.com/ARMmbed/mbedtls;tag=mbedtls-2.4.2" ... bb.data_smart.ExpansionError: Failure expanding variable SRCPV, expression was ${@bb.fetch2.get_srcrev(d)} which triggered exception FetchError: Fetcher failure: Conflicting revisions (abeccb9dbd7e19ae91ac50e1edd3803111c5f9b6 from SRCREV and mbedtls-2.4.2 from the url) found, please specify one valid value ----- snip ----- Assuming the tag is valid, we should get the tag commit hash and drop the usage of 'tag=' from SRC_URI. By using a commit hash corresponding to the tag will prevent bitbake from accessing remote repository in order to expand SRCPV. Signed-off-by: Chang Rebecca Swee Fun <rebecca.swee.fun.chang@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18mesa: Upgrade to 17.2.6 stable releaseOtavio Salvador2
This upgrades the recipe to 17.2.6 bugfix release. The changes can be seen at: https://www.mesa3d.org/relnotes/17.2.6.html Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18libxslt: remove inappropriate patchRoss Burton2
This was patching -lxslt directly into the pkgconfig file, but XSLT_LIBS already contains this so the patch is redundant. Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18libxslt: use HTTP instead of FTP in SRC_URIRoss Burton1
FTP isn't as reliable as HTTP. [ YOCTO #12398 ] Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18icu: fix libicudata corruption on big endian systemYi Zhao1
ICU library libicudata is created with a wrong endianness if the host and target have different endianness. (e.g. build ICU for qemuppc on x86-64 host) See upstream bug report: http://bugs.icu-project.org/trac/ticket/11758 The discussion in oe-core mailing list: https://www.mail-archive.com/openembedded-core@lists.openembedded.org/msg65155.html The root cause is the native pkgdata can not generate correct icu data for different endianness. By default, this data is built into the shared library libicudata that would cause it corrupt. But ICU also provides additional options for loading the data. With option --with-data-packaging=archive, ICU outputs a single icudt.dat file which can be loaded by the library. See document: http://userguide.icu-project.org/icudata So for big endian system, we can use the separated data file which re-generates by icupkg and set the correct ICU_DATA environment variable to make sure the library can load the data without problems. Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18autoconf: Override config.guess/.sub in source treeNathan Rossi1
autoconf has not been released in a number of years. However many changes have been made to the gnu-config config.guess/.sub since 2.69, including new architectures, OS variants, etc. In order to enable these targets without creating patches for the source itself populate the gnu-config files from the sysroot as is done with autotools recipes. Whilst it is not possible for the autoconf recipe to bootstrap its configure task (using the autotools_do_configure), the files can be manually copied into the target location. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18ovmf: Fix build failure for PARALLEL_MAKE with no spaceJason Wessel1
The ovmf package fails to build if you use a PARALLEL_MAKE flag without a space in it. If you put the following in local.conf for example: PARALLEL_MAKE = "-j4" The build will fail with as follows: | build.exe: error: Option -n only allows one instance in command line! | WARNING: /opt/build/ovmf/git-r0/temp/run.do_compile.26080:1 exit 2 from '/opt/build/ovmf/git-r0/git/OvmfPkg/build.sh $PARALLEL_JOBS -a $OVMF_ARCH -b RELEASE -t ${FIXED_GCCVER}' | ERROR: Function failed: do_compile (log file is located at /opt/build/ovmf/git-r0/temp/log.do_compile.26080) The failure is because the build.sh expects a space. The simple work around is to fix the recipe to add some white space. The build.sh only cares that it gets at least one space between the arguments, the extra space if someone uses "-j 4" does not cause problems. Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18glib-2.0: fix for non-utf8 encoded filesJackie Huang2
Some source files aren't valid utf-8 containing for example iso8859-1 accented characters in author's names. Replace invalid data with a replacement '?' character and print a warning to keep things working. Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18prelink_git.bb: Update recipe to newest commitNathan Rossi1
Update prelink to the newest commit on the cross_prelink ref. This includes the following changes: 05aeafd053 Disable automatic generation of prelink.pdf aa2985eefa src/rtld: Add MicroBlaze support based on glibc-2.24 62f80843f8 README: update information on reloc8/reloc9 failures The primary purpose of this update is to enable the added MicroBlaze rtld support so as to enable gobject-introspection for MicroBlaze. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18coreutils: add PACKAGECONFIG for single-binaryChen Qi1
Add PACKAGECONFIG for single-binray. Disable it by default. When enabled, there would only be one binary file /usr/bin/coreutils, other files like 'ls' are text files containing contents like: #!/usr/bin/coreutils --coreutils-prog-shebang=ls And the size of the rpm package reduces from 849K to 519K. Default to disable this option to keep the traditional behaviour. Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18coreutils: upgrade to 8.28Chen Qi2
Upgrade coreutils to 8.28. Backport a patch to fix the following build error on centos7. warning: unreferenced node `Realpath usage examples' Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18targetcontrol.py: use oe.types.boolean for QEMU_USE_KVMRobert Yang2
So that both QEMU_USE_KVM = "True" and "1" will work. [YOCTO #12343] Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18libunistring: upgrade to 0.9.8Maxin B. John2
Refreshed the following patch: iconv-m4-remove-the-test-to-convert-euc-jp.patch No change in license as update in License Checksum is due to change in Copyright years. Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18orc: upgrade to 0.4.28Maxin B. John1
0.4.27 -> 0.4.28 Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18mc: upgrade to 4.8.20Maxin B. John2
Remove backported patch: 0002-Ticket-3697-tty_init-unify-curses-initialization.patch Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18ffmpeg: update to 3.4Alexander Kanavin2
Schroedinger support has been dropped: https://git.ffmpeg.org/gitweb/ffmpeg.git/commitdiff/220b24c7c9 Remove upstreamed patch. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2017-12-18psmisc: update to 23.0Alexander Kanavin6
Switch to gitlab, as that's where development now happens. Drop two upstreamed patches, add apatches to avoid newly introduced build errors, and a gettext fix suggested here: http://lists.openembedded.org/pipermail/openembedded-core/2017-November/144566.html Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2017-12-18webkitgtk: update to 2.18.3Alexander Kanavin10
gcc7.patch, musl-fixes.patch, and ppc-musl-fix.patch all change code that is no longer present in upstream tree. However, a patch with different musl fixes has been added. The rest of the patches are rebased to the new tree. Libtasn is a new dependency. Disable Gstreamer GL support on x86 due to clashing headers problem. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2017-12-18gobject-introspection: update to 1.54.1Alexander Kanavin1
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2017-12-18gstreamer1.0-plugins-bad: remove redundant Wayland patchRoss Burton2
The installation path and wayland-scanner location problems in Wayland were resolved in "wayland: Fix installation patch issue" (oe-core 14c0d99) which made the WAYLAND_PROTOCOLS_SYSROOT_DIR workaround redundant. Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18xserver-xorg: remove redundant Wayland patchRoss Burton2
The installation path and wayland-scanner location problems in Wayland were resolved in "wayland: Fix installation patch issue" (oe-core 14c0d99) which made the WAYLAND_PROTOCOLS_SYSROOT_DIR workaround redundant. Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18gtk+3: remove redundant Wayland patchRoss Burton2
The installation path and wayland-scanner location problems in Wayland were resolved in "wayland: Fix installation patch issue" (oe-core 14c0d99) which made the WAYLAND_PROTOCOLS_SYSROOT_DIR workaround redundant. Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-18weston: remove patch that isn't applied anymoreRoss Burton1
This patch was removed from SRC_URI in the Weston 3.0 upgrade (148920f) but the patch wasn't deleted. Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-13python-scons: upgrade to v3.0.1; use pypi.bbclassTim Orling3
* Simplify recipe by using pypi.bbclass * Drop patch for __future__ print_function - fixed upstream: https://github.com/SConsProject/scons/pull/1/commits/4c199d06e76afb9379e76942d0f68caa57f42509 Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2017-12-13python3-iniparse: use pypi.bbclassTim Orling1
* Simplify recipe by using pypi.bbclass Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
generated by cgit v1.2.3 (git 2.25.1) at 2025-03-31 12:34:32 +0000