summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* maintainers.inc: remove packages that are no longer in oe-coreAlexander Kanavin2015-09-121-2/+0
| | | | | | | | (From meta-yocto rev: 613c38fb9b5f20a89ca88f6836a21b9c7604e13e) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky-tiny.conf: Require utmpx, its needed for busyboxKhem Raj2015-09-121-1/+1
| | | | | | | | | | | | | This libc feature is a basic need and prerequisite for busybox fix for [YOCTO #8243] to be merged [YOCTO #8243] (From meta-yocto rev: b24f3d01759642340887b7487f36939125c14b06) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* maintainers: add maintainer info for new webkitgtk, epiphany and their ↵Alexander Kanavin2015-09-122-3/+12
| | | | | | | | | dependencies (From meta-yocto rev: e10ff3acdae3cfbee4a207a0e7e8e850d02b5918) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-worker: Ensure pipe closure doesn't crash before killpg()Richard Purdie2015-09-121-1/+5
| | | | | | | | | | If the pipe is closed, we want to ensure that we kill any child processes by triggering the sigterm handler before we exit. This code does that, hopefully avoiding the remaining process left behind issues on the autobuilder. (Bitbake rev: 60f6c2818f38c4d9c2d9aaa42acf3071636f4a3b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: toaster: increase waiting timeEd Bartosh2015-09-121-2/+2
| | | | | | | | | | | | | Increased waiting time for toasterUI from 10 to 25 seconds. Bitbake takes longer time to start, so toaster should wait longer. [YOCTO #8240] (Bitbake rev: 224ee3685fe20915b21d299ab80f7b289a916dca) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: brian avery <avery.brian@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* testimage: Handle core-image-lsb-sdk qemumips test restrictionRichard Purdie2015-09-121-4/+9
| | | | | | | | | | On qemumips, some tests are slow to the point of the autobuilder appearing hung. We therefore specifically exclude buildsudoku but to do this, we need to list the tests we expect to work on core-image-lsb-sdk. (From OE-Core rev: cf03765705c6cd26c1a904b62b9aca8f914f44aa) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/targetbuild: Ensure we run gnu-configize so config files are up to dateRichard Purdie2015-09-121-3/+3
| | | | | | | | | On aarch64 we need to do this as the versions in the upstream source don't recognise the target triplet causing SDK test failures. (From OE-Core rev: 2374bfa3b98f787f4559f14a60647e4c2b051274) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_base: Fix aarch64 OLDEST_KERNEL sdk issuesRichard Purdie2015-09-121-1/+6
| | | | | | | | | | | | | | | | aarch64 sets OLDEST_KERNEL to 3.14. This stops the aarch64 SDK installing on anything with an older kernel which is clearly incorrect. I attempted to extract the correct non-overridden version from the data store but it proved problematic and I was running into data store issues. Those are a separate problem but there isn't time to fix this right now. Instead just code the SDK kernel version separately to work around this for now (and fix the autobuilder tests and SDK usage). (From OE-Core rev: 522ba4c51fff53566678b2689d0d63c393e417b3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* testimage: Fix SDK extraction error handlingRichard Purdie2015-09-121-1/+4
| | | | | | | | | Currently if the SDK fails to extract, no error is shown and the test is marked as passed! Clearly this is incorrect, fix it to correctly raise an error. (From OE-Core rev: fb2235a21e45fa1a47c3b7a9a6a72c515ef10dd1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* devtool: update-recipe: get srcuri parameters with decodeurl()Markus Lehtonen2015-09-121-5/+2
| | | | | | | | | | Use already existing bb.fetch.decodeurl() for getting the parameters for a URI. This is more fault tolerant and maintainable. (From OE-Core rev: cd201664b827e37fcabca272262016b171e997d9) Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "ptest: use fakeroot for do_install_ptest_base"Ross Burton2015-09-121-1/+1
| | | | | | | | | | This reverts commit 56c5fa106eeccda2ca92dbeb73ff01ba40992e7d. (This fix was incorrect and there is a better fix due to be merged) (From OE-Core rev: 21e044d92e927639a574c43cf7778e31f2e66377) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* u-boot.inc: Add host compiler flags and openssl-native dependencyNathan Rossi2015-09-121-0/+7
| | | | | | | | | | | | | | U-Boot will compile its own tools during the build, with specific configurations (aka when CONFIG_FIT_SIGNATURE is enabled) the host tools require openssl. This patch adds 'openssl' as a PACKAGECONFIG that enables the use of openssl-native as a dependency and also adds the HOSTCC flags that U-Boot uses when compiling the host tools. (From OE-Core rev: 7d0edf5d04fba0b642bfb08a1de28fbc8e480209) Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-compare: add support for examining deb and ipk packagesPaul Eggleton2015-09-122-3/+69
| | | | | | | | | | | | This is just rudimentary support at the moment as we'd potentially want to compare the control files a bit more specifically than this does, but it's a start. (From OE-Core rev: 60564c6d6b8c1a3813baa04fb0d5597cf63f2a9f) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/sstate: break out function to get sstate manifest filenamePaul Eggleton2015-09-122-5/+14
| | | | | | | | | | | | It is useful in a few different contexts to see which files have been written out by an sstate task; break out a function that lets us get the path to the manifest file easily. (From OE-Core rev: 090196dd2d8f4306b34b239e78c39d37cc86034c) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: avoid image file name mismatchesPatrick Ohly2015-09-121-16/+16
| | | | | | | | | | | | | | | | | Giving anything with -image in it as bootparams or in qemuparams (for example, an additional -drive parameter with an image file or an "-initrd .../core-image-minimal-initramfs-qemux86.cpio.gz") caused runqemu to treat these parameters as names of the rootfs image file. Matching *-image) after checking the current argument for more specific cases like bootparams and qemuparams avoids this misinterpretation of the command line parameters. (From OE-Core rev: 29e0aaa7345ca823bb4af2d4a870e98ac75e04e7) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* u-boot.inc: Add U-Boot ELF install and deployNathan Rossi2015-09-121-1/+62
| | | | | | | | | | | | | | | | | Add support for U-Boot recipes to install and deploy the generated ELF files for each config. The U-Boot ELF's are useful for debugging, and booting (directly booting, e.g. by JTAG or using QEMU) and complement the generated binary image. This additional feature is disabled by default, machines/etc that want to use it need to set UBOOT_ELF to the corresponding ELF file (generally u-boot or u-boot.elf depending on the architecture) (From OE-Core rev: fae697dedf6ab04b7c123ea5615b1003a79c2422) Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* connman: upgrade to 1.30Cristian Iorga2015-09-122-49/+2
| | | | | | | | | | | | | Bugfixes. build-create-dirs-before-putting-files-in-them.patch patch removed, patch included upstream. (From OE-Core rev: 080ae179e1de7f507263c550de8c02e3e224a964) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initramfs-framework: support dropping into shell on failurePatrick Ohly2015-09-121-0/+4
| | | | | | | | | | | | | | | | | When the init_fatal_sh boot parameter is present (i.e. used without value) and a fatal problem occurs inside the initramfs-module, a shell will be started instead of looping forever. Useful for debugging. Interestingly enough, the code was already indented to support such an if check... (From OE-Core rev: 1d3dc681e809846dba7cae4f81566045a3f8c205) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initramfs-framework: support init boot parameterPatrick Ohly2015-09-121-1/+1
| | | | | | | | | | | | | It can be useful for debugging to override the default /sbin/init. This is something typically done via the init boot parameter which then gets interpreted by the kernel. But when using an initramfs, it is the initramfs which must react to the option. (From OE-Core rev: dfd6d4c765924f472ac2df724342547b5c15249a) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initramfs-framework: support ro boot parameterPatrick Ohly2015-09-121-0/+6
| | | | | | | | | | | | | | | | Default is to mount the rootfs read/write. "ro" can be used to turn that into read-only, which is useful on systems where userspace does an fsck before remounting read-write. Giving both "ro" and "rw" will still mount read-only regardless of the order, because the ordering information is not preserved by the initramfs-framework's boot param support. (From OE-Core rev: a09f10f9360862c16fb68972ac041d474d6e3a64) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initramfs-framework: support rootflags and rootfstype boot parameterPatrick Ohly2015-09-121-1/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | These two parameters are supported by the kernel (https://www.kernel.org/doc/Documentation/kernel-parameters.txt). When an initramfs is used, the kernel does not mount the rootfs and the initramfs needs to react to them. The boot parameters can be set both by the image creator and by users. Supporting these two parameters is useful: - rootflags is needed to ensure that the rootfs is already mounted as intended in the time between starting init and init remounting it (as systemd does); this is critical for IMA where iversion must be active already when system starts writing files. - setting it correctly up-front avoids messages from the kernel ("cannot mount ... as ext2 because ...") when trying to guess the desired type. For example, assuming that only one of ext4/ext3/ext2 is set, rootfstype could be set in an image recipe with: APPEND_append = "${@''.join([' rootfstype=' + i for i in ['ext4', 'ext3', 'ext2'] if i in d.getVar('IMAGE_FSTYPES', True).split()])}" (From OE-Core rev: b8ea1c61b4b8071edf70f5d42119c54ea84de330) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* directfb: Avoid using VLAs and printf formatsKhem Raj2015-09-122-1/+64
| | | | | | | | | | These are not portable features and are flagged by clang (From OE-Core rev: 8a577fa7cf54db646f4e61f383390054e5f04ca3) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mdadm: Fix bugs exposed by clangKhem Raj2015-09-122-0/+87
| | | | | | | | | clang points to coding errors which otherwise go unnoticed (From OE-Core rev: 3738dbf4d204e1c4f1dd2fad6a76291ffbbc414e) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sudo: Disable rsize_t deliberatelyKhem Raj2015-09-121-0/+1
| | | | | | | | | | | | gcc does not have it but clang does, problem happens when host compiler is gcc and cross compiler is clang, because autoconf detects it with clang and slaps it to host compiler as well (From OE-Core rev: c70d915bcc3054120e7ad06b9bcfef57f2d15371) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* puzzles: Fix build with clangKhem Raj2015-09-122-0/+47
| | | | | | | | | | | Clang uncovered an error where abs() is used on long types, we shoud be using labs() (From OE-Core rev: cb92ac5389ed3cecf13158a0150e211b5392aba7) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kexec-tools: Pass -r directly to linkerKhem Raj2015-09-122-0/+33
| | | | | | | | | | | -r is understood by gcc but not by clang, anyway its a linker option so pass it straight to linker by using -Wl explicitly (From OE-Core rev: 3f4ab836d7d9b7a994b65ab8c7ebf6ff65e6277b) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* alsa-tools: Fix compiling with clangKhem Raj2015-09-122-0/+32
| | | | | | | | | | | | | Fixed a linking error occurring when building with clang, where a function reference is emitted but function is not since its marked as inline, making it static inline gives better opportunity to compiler to compile it (From OE-Core rev: 890fa3d0e71f951993252f5b94e2211b4b06670e) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* latencytop: Fix build with clangKhem Raj2015-09-122-2/+68
| | | | | | | | | | | Clang is stricter with syntax checking and flags the functions return values if they dont match with function signatures, Fixed thusly (From OE-Core rev: 91b8c2900570720d56a123a90e927f49a6a6095f) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ccache: Dont add LDFLAGS to compiler flagsKhem Raj2015-09-121-2/+0
| | | | | | | | | | | This is no longer required, its been carried over for a long time. As a side effect it helps compiling ccache with clang (From OE-Core rev: f8d3122e9d194aa7fdf5c4c645edfcc7fdcb9ccc) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bdwgc: Include signal.h instead of hard asm/sigcontext.hKhem Raj2015-09-122-1/+38
| | | | | | | | | | | | All cases are about glibc and for non-glibc systems it falls back to last else choice which still is glibc's older version, ideally it should have a case where libc != glibc (From OE-Core rev: 3140a731d36adbf5be9f988f25653304ac86676e) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* minicom: Fix build with muslKhem Raj2015-09-122-0/+48
| | | | | | | | | | | musl exposes the inherent assumption about certain header files from glibc (From OE-Core rev: 77789bdd0f55714590d95589558edc8151f9860d) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* man: Use -DSYSV when builing for linuxKhem Raj2015-09-121-0/+2
| | | | | | | | | | | | We needed this define but were getting away since glibc indirectly included fcntl.h but man sources clearly guard inclusion of fcntl.h with SYSV, this is uncovered with musl (From OE-Core rev: 34682843d0e2b645d33900ee425428a01e3f2ddc) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sudo: Include sys/types.h for id_t definitionKhem Raj2015-09-122-0/+35
| | | | | | | | | | | This is exposed by musl, on glibc sys/types.h comes as indirect include from other include myriad. (From OE-Core rev: 7a55d298376b83248a4a35f3c01f3fd163908046) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* slang: Fix namespace conflict vis-a-vis posix_closeKhem Raj2015-09-122-0/+40
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes errors like | /home/ubuntu/work/oe/openembedded-core/build/tmp-musl/work/core2-64-oe-linux-musl/slang/2.2.4-r12/slang-2.2.4/src/slpo sio.c:366:12: error: conflicting types for 'posix_close' | static int posix_close (SLFile_FD_Type *f) | ^ | In file included from /home/ubuntu/work/oe/openembedded-core/build/tmp-musl/work/core2-64-oe-linux-musl/slang/2.2.4-r1 2/slang-2.2.4/src/slinclud.h:20:0, | from /home/ubuntu/work/oe/openembedded-core/build/tmp-musl/work/core2-64-oe-linux-musl/slang/2.2.4-r1 2/slang-2.2.4/src/slposio.c:24: | /home/ubuntu/work/oe/openembedded-core/build/tmp-musl/sysroots/qemux86-64/usr/include/unistd.h:38:5: note: previous de claration of 'posix_close' was here | int posix_close(int, int); | ^ | make[1]: *** [/home/ubuntu/work/oe/openembedded-core/build/tmp-musl/work/core2-64-oe-linux-musl/slang/2.2.4-r12/slang- 2.2.4/src/elfobjs/slposio.o] Error 1 (From OE-Core rev: 6b0cebe506b73cee7591089b624b69e009100c89) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* irda-utils: Weak Define the build TARGETSKhem Raj2015-09-121-4/+7
| | | | | | | | | | | | | This will help one to disable the targets via bbappends if needed e.g. musl can not compile irdaping since it uses includes net/if_packet.h, which (on GLIBC) only defines struct sockaddr_pkt but not in other libc e.g. musl that makes irdaping specific to glibc (From OE-Core rev: 6369bff034a6ee8fbf7fd47d3f9ba46c3ac1a367) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bjam-native: build and install bjam.debugWenzong Fan2015-09-122-1/+54
| | | | | | | | | | | | | | | | | | | bjam is stripped by default, this causes QA warning while stripping it from do_populate_sysroot(): WARNING: File '.../tmp/sysroots/x86_64-linux/usr/bin/bjam' \ from bjam-native was already stripped, \ this will prevent future debugging! The JAM scripts allow to build unstripped version with '--debug'. Just build and install the bjam.debug to stop bjam from being stripped in compile step. (From OE-Core rev: e7147de9f28925b1bb5df39d9c0848dd7957328c) Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-5.2: remake 0040-nativesdk-gcc-support.patchRobert Yang2015-09-121-75/+67
| | | | | | | | | | It couldn't be applied by sled11's patch, now fix it. (From OE-Core rev: e01b450a419aba2164a86510ca1ae402ec86aff0) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bind: fix compile failure when building path is longChen Qi2015-09-122-0/+26
| | | | | | | | | | | | | | | | Fix the building path is long, when building bind, we would meet the following error. ".../long/path/to/bind/9.10.2-P3-r0/bind-9.10.2-P3/lib/dns" too long This is because the in gen.c, DIRNAMESIZE is limited to 256. But in OE, the path length limit is more than 400. So we change it to 512. (From OE-Core rev: 2f22eb1ce8083afb929cce432b8dda84682520e8) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: only fetch remote signatures if verification is enabledRoss Burton2015-09-121-3/+6
| | | | | | | | | | | | Only fetch remote signatures if verification has been enabled, as otherwise the fetcher throws errors that sstate.bbclass can't ignore. [ YOCTO #8265 ] (From OE-Core rev: aa8ba5c4af2636dbc2d0c1ad9c230e8aa26d9962) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "boot-directdisk.bbclass: use rootfs UUID by default"Patrick Ohly2015-09-121-1/+1
| | | | | | | | | | | | | | | | | This reverts commit 8ca8e2e5bf4a9f01dc48300149a8e1d71d715400. Further testing showed the kernel does not support root=UUID; it is something typically handled by the initramfs. Because boot-directdisk.bbclass cannot know whether it is using a suitable initramfs, root=UUID cannot be the default. Instead, it will have to be set in image recipes on a case-by-case basis. (From OE-Core rev: 8478024bd25651aa866d4582dcc193d51553554a) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ptest: fix file ownerships in ${PTEST_PATH}Ross Burton2015-09-121-0/+1
| | | | | | | | | | | | | | | | | | | As most upstreams don't have installable test suites it's fairly common to copy files directly out of a source tree for ptests, but this results in files in the recipe being owned by the user running bitbake: WARNING: QA Issue: .../sed/4.2.2-r0/packages-split/sed-ptest/usr/lib64/ sed/ptest/testsuite/bug-regex21 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated] Instead of needing to fix this in every recipe that has this problem simply chown the files to root:root in do_install_ptest_base. (From OE-Core rev: 552daf60c58784c8f1acc12c5a443a44a922f743) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: Define OECORE_MACHINE_SYSROOT on setup_sysrootLeonardo Sandoval2015-09-121-1/+12
| | | | | | | | | | | | | | | | | | | | | | | | At least the OVFM (UEFI Firmware for Qemu and KVM) recipe stores the BIOS under $OE_TMPDIR/sysroots/$MACHINE, now defined as OECORE_MACHINE_SYSROOT. The latter is used when searching BIOS, VGA BIOS and keymaps. As a example, to boot a OVFM BIOS, one can run the following command: $ runqemu qemux86-64 core-image-minimal \ biosdir=usr/share/ovmf \ biosfilename=bios.bin \ nographic Note the bios* parameters: these two are needed to specify the subfolder (parent folder is OECORE_MACHINE_SYSROOT) and BIOS filename (without it, it picks a BIOS named bios-256k.bin). [YOCTO #5654] (From OE-Core rev: bded344a464bb854db3935da1f6a3320e5aa01e5) Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gnome-icon-theme: remove the recipeAlexander Kanavin2015-09-122-50/+0
| | | | | | | | | | It is not used by anything in oe-core and will be moved to meta-gnome (From OE-Core rev: 9dde1ce547c8be064ff63ac832f62a08a9b00f10) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pcmanfm: add an icon theme dependencyAlexander Kanavin2015-09-121-0/+2
| | | | | | | | (From OE-Core rev: 041b717d73a8edf838392c23c21dbcc26c7ff50d) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa: Test failure/cleanup improvementsRichard Purdie2015-09-121-0/+1
| | | | | | | | | | | | | | | | | | | Currently, if qemu segfaults, the tests merrily continue trying to execute which takes time for them to timeout and is a bit silly. Worse, no logs about the segfault are shown to the user, its silent! This patch tries to unravel the tangled web of issues and ensures that we: * install a SIGCHLD handler which tells the user qemu exited * check if qemu is running, if it isn't fail the test outright * don't leave processes behind in sshcontrol which would hold bitbake.lock and block shutdown (From OE-Core rev: 77e9363feba53b72429154be5713c46b007ae0a4) (From OE-Core rev: c77b57e2fa8a4cf90543038fe1939f6ca9b12bd1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perf: fix the install-python_extRoy Li2015-09-121-1/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. $(grep xxx xxx) never returns 0, it maybe return empty or string, and can not compare with 0, this fixes that python module never are installed. 2. python library is installed into /usr/lib/ by default, but we expect it is installed into ${libdir}, so add --install-lib parameter for python setup.py to set the library dir; this fixes not shipped warning, since python modules are installed into /usr/lib/, but FILE_${PN}-python expects it is under ${libdir}, which is /usr/lib64/ for 64bit machine 3. the makefile target install-python_ext is moved from Makefile to Makefile.perf from linux v3.13, so match install-python_ext in Makefile.* and --root='/\$(DESTDIR_SQ)' before linux v3.13 will install the target python library to native sysroot, so replace it with --prefix as after linux 3.13; this fixes not shipped warning, and install target files to native dir, like below: ERROR: QA Issue: perf: Files/directories were installed but not shipped in any package: /home /home/pokybuild /home/pokybuild/yocto-autobuilder /home/pokybuild/yocto-autobuilder/yocto-worker /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots/x86_64-linux /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots/x86_64-linux/usr /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots/x86_64-linux/usr/lib /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots/x86_64-linux/usr/lib/python2.7 /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots/x86_64-linux/usr/lib/python2.7/site-packages /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots/x86_64-linux/usr/lib/python2.7/site-packages/perf.so /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-ppc-lsb/build/build/tmp/sysroots/x86_64-linux/usr/lib/python2.7/site-packages/perf-0.1-py2.7.egg-info (From OE-Core rev: 43f965061f8af4c4537e9d9c0257253e613a616d) Signed-off-by: Roy Li <rongqing.li@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* packagegroup-core-nfs: provide the nfs-client IMAGE_FEATURESRoy Li2015-09-123-2/+8
| | | | | | | | | | | provide the nfs-client IMAGE_FEATURES, to ease a user to only install nfs client related files to image (From OE-Core rev: bbdc808a8ea76369a36473c906991e25ca49c323) Signed-off-by: Roy Li <rongqing.li@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gstreamer1.0: Fix QoS/lateness checking if subclass implements ↵Yuqing Zhu2015-09-122-0/+71
| | | | | | | | | | | | | | prepare/prepare_list vfuncs In function gst_base_sink_chain_unlocked(), it should calculate jitter based on current media clock, rather than just passing 0. Or it will drop all the frames when rewind in slow speed, such as -2X. (From OE-Core rev: 68591de72e27a985242d6ff19fffb80f69869003) Signed-off-by: Yuqing Zhu <b54851@freescale.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gstreamer1.0: Fix sticky events haven't been sent out when active track ↵Yuqing Zhu2015-09-122-0/+168
| | | | | | | | | | | | | reach EOS EOS event hasn't been sent to down-element. The resolution is block EOS event of inactive pad, sending the event after the pad actived. (From OE-Core rev: 19a2016bff489809af4852a20b9feebcc835a446) Signed-off-by: Yuqing Zhu <b54851@freescale.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* externalsrc.bbclass: better filtering of cleandirsMarkus Lehtonen2015-09-121-11/+7
| | | | | | | | | | | | | | We really do not want our (external) source tree to be removed. There might be multiple values in the 'cleandirs' varflag pointing to our source tree - causing it to be wiped out. This patch improves the filtering of 'cleandirs' by examining the expanded values inside it. Any (expanded) values pointing to our source tree get removed. (From OE-Core rev: eec871fe405e140a1919999fe2f4cf24f1839e5d) Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-15 14:25:21 +0000