summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* dhcp: use ${PN} for SYSTEMD_SERVICESChen Qi2014-09-291-5/+5
| | | | | | | | | | | | We should use ${PN} instead of hardcoding 'dhcp' for SYSTEMD_SERVICES, otherwise we would have 'installed-not-shipped' QA error if we are building lib32-dhcp. (From OE-Core rev: c3a152f946f7cb1666384fd7a214f883cbaecb56) 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>
* volatile-binds: use ${PN} for SYSTEMD_SERVICEChen Qi2014-09-291-1/+1
| | | | | | | | | | | | As this recipe inherits allarch, it makes no real difference whether we are using ${PN} or 'volatile-binds'. But using ${PN} would keep the same style with the other recipes in OE. (From OE-Core rev: 708cc039b6cc891e466e89d2b10fcdea6c19287c) 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>
* acpid: use ${PN} for SYSTEMD_SERVICEChen Qi2014-09-291-2/+1
| | | | | | | | | | | | We should use ${PN} instead of 'acpid' for SYSTEMD_SERVICE, otherwise we would have the 'installed-not-shipped' QA error if multilib is enabled and we run `bitbake lib32-acpid'. (From OE-Core rev: f8217853c69cf06c92b2f3885f7d49851213188f) 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>
* packagegroup-core-standalone-sdk-target: Add libgcov-dev to on device SDKNobuhiro Iwamatsu2014-09-291-0/+1
| | | | | | | | | | | | | | | | When a user takes coverage in gcc of SDK, it becomes the link error in SDK because there is not libgcov. ---- ld: cannot find -lgcov collect2: error: ld returned 1 exit status ---- (From OE-Core rev: 99b26dba6e4f5a64579f183883265498000e3104) Signed-off-by: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gnomebase: fix indentationRoss Burton2014-09-291-7/+7
| | | | | | | (From OE-Core rev: 103ded50380916d210e293913eebb173f014063e) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* syslog: Change unused variable declaration LOCAL=0 to LOG_LOCAL=1Michael Gloff2014-09-291-1/+1
| | | | | | | | | | This fix allows the correct appending of -L to syslogd arguments when both file and remote logging are selected. (From OE-Core rev: ca68019760de6c5d5401be8eae7e65e7e6ca9021) Signed-off-by: Michael Gloff <mgloff@emacinc.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qtdemo-init: Make qtdemo startup correctlyYi Zhao2014-09-291-5/+5
| | | | | | | | | | The qtdemo can't launch via qtdemo-init initscript. Fix it. (From OE-Core rev: bdd7a07db6b41c6c87c272d410af63c2d0251fc8) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perf: fix issue about package splittingChong Lu2014-09-291-1/+3
| | | | | | | | | | | | Currently, perf can't split to perf-archive, perf-tests, perf-python and perf-perl. All files are included in perf package. Change the perfexecdir variable to make split successfull. Add python to RDEPENDS_perf-tests. (From OE-Core rev: 32fcc621401e7761d9b96bc5b7bef143c1c29695) Signed-off-by: Chong Lu <Chong.Lu@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libpam / xtests: remove bash dependencyWenzong Fan2014-09-292-1/+228
| | | | | | | | | | | | | | | | | There's not bash specific syntax in the xtests scripts: $ cd Linux-PAM-1.1.6/xtests # replace /bin/bash to /bin/sh and check the bashisms: $ checkbashisms *.sh No output So the runtime dependency to bash could be removed. (From OE-Core rev: 1917bf7aa74aa1b86756c73c56537db2591115e5) 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>
* gst-plugins-base: fix build failure for x86Jackie Huang2014-09-292-1/+40
| | | | | | | | | | | On x86, EMMINTRIN is defined but not usable without SSE so check for __SSE__ and __SSE2__ as well. (From OE-Core rev: 556a19423d15c7c13f60d57528a3b880f95750b9) Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* coreutils: selinux/flask.h should respect to with_selinuxRobert Yang2014-09-292-0/+40
| | | | | | | | | | | | | | Fixed when build with meta-selinux even with --without-selinux: runcon.c:49:28: fatal error: selinux/flask.h: No such file or directory # include <selinux/flask.h> ^ compilation terminated. (From OE-Core rev: d52a606c8a75496f3b7239adc19fdb66e3ae576a) 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>
* systemd: disable resolv.conf symlink unless resolved is enabledPeter A. Bigot2014-09-292-0/+36
| | | | | | | | | | | | | | | | | | | | The tmpfiles configuration in systemd unconditionally creates a symlink from /etc/resolv.conf to the location where systemd's resolved service will place the real file. This link is only appropriate when resolved is enabled and running: its presence prevents connman or other systems from providing a working resolv.conf when systemd is not assigned that responsibility. OE has not yet enabled systemd's networkd or resolved by default. There is a TODO in the systemd source to fix this, but it has not been addressed upstream. This patch comments out the corresponding line when resolved is not enabled in the package configuration. (From OE-Core rev: 7e2b05a6f59209687829225878a19a1dad8143b9) Signed-off-by: Peter A. Bigot <pab@pabigot.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Change overlapping files warning to a fatal errorRichard Purdie2014-09-291-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | When files overlap in the sysroot, something bad usually happened. We've had two independent cases recently where a couple of months after one of these warnings was shown, builds failed due to corruption. This change moves the warning to become a fatal error. The complaint I've had about this is that we need to tell the user what happened and more importantly how to recover from it. If we could recover from it, great but the trouble is we simply don't know what happened. As a compromise, we can document several of the possible scenarios in the error message. We don't normally go to this level of detail however in this case, I'm lacking other viable alternatives. I do believe it is important to stop as corruption occurs rather than letting the build contunue into territory that is not deterministic amongst other things. The complex message is followed by a simpler one in case the long message is too much for the user. (From OE-Core rev: 179ac7de03977b6e440409eddb2166819e07286a) (From OE-Core rev: 4b503f25f1ef8f554d3c76d88399db379dc818cc) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: prserv/serv: Improve error message when prserver cannot bind to ↵Konrad Scherer2014-09-291-2/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | supplied host address If localhost resolves to a remote address (due to a misconfigured network), starting the pr server will fail without useful information. To reproduce, add '<bogus ip> localhost' to /etc/hosts and run 'bitbake -p'. The error message will be: ERROR: Timeout while attempting to communicate with bitbake server ERROR: Could not connect to server False: Running 'bitbake-prserv --host=localhost --port=0 --start' will fail with: error: [Errno 99] Cannot assign requested address Since these errors does not show the IP address of the attempted socket binding, this results in a lot of wasted time looking at firewall rules, etc. This patch results in the following error message if the socket binding fails: PR Server unable to bind to <bogus ip>:0 (Bitbake rev: fae5914030bcf4c061c22fc61034c40c87b7121a) Signed-off-by: Konrad Scherer <Konrad.Scherer@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hob: Fix sstate mirrors manglingRichard Purdie2014-09-291-4/+1
| | | | | | | | | | | | hob was adding the redundant characters "\1" in SSTATE_MIRRORS variable. If needed it is expected the user will add this instead so remove the code that was doing this. [YOCTO #6600] (Bitbake rev: 73bf120062fc00c7e26dc4e77a7d140658d89daf) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch: Extend testing of subdir unpack parameter and fixRichard Purdie2014-09-292-0/+9
| | | | | | | | | This fixes urls of the form file://some/path/file;subdir=b. It also adds in a couple of tests so we now tests these corner cases. (Bitbake rev: 46306912a96444790efa9418d934dfdd36773ba1) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch: SRC_URI parameter "subdir" does not work for local filesRoxana2014-09-291-1/+4
| | | | | | | | | | | Check if the 'subdir' parameter exists and assign it to 'destdir' so that files are copied in ${WORKDIR}/destdir. This fixes urls that are of the form file://a;subdir=b. (Bitbake rev: 836a986b365eb9798563ec08d90b346596de7791) Signed-off-by: Roxana Ciobanu <roxana.ciobanu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: monitordisk: don't log when not monitoring a filesystem for inodesRoss Burton2014-09-291-4/+2
| | | | | | | | | | | | Writing a log that the filesystem isn't being monitored for inode usage just confuses users who are not aware about the nature of inodes in their filesystem, so don't say anything, just silently disable the monitor. In general this only happens on filesystems which don't have a limit on inodes. (Bitbake rev: ca93bc84ee5fb94a50c11c47e4d212d7da649e24) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to dizzy head revisionRichard Purdie2014-09-231-1/+1
| | | | | | (From OE-Core rev: e6c6d3fcfd2faf867e8145d25c1ba197fb9ee6b5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky.conf: Bump version for 1.7 dizzy releaseRichard Purdie2014-09-231-2/+3
| | | | | | (From meta-yocto rev: aa6a779bbda84b53587979cc400aa4d30afbf03a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bin/bitbake: Update to version 1.24.0Richard Purdie2014-09-232-2/+2
| | | | | | (Bitbake rev: 637ce8df2658e4905fab8a0600a45505596bf472) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sanity.conf: Update minimum bitbake version to 1.23.2 due to event changesRichard Purdie2014-09-231-1/+1
| | | | | | (From OE-Core rev: b4e2a769e8def2e78ffca3f006a0cc88407aaeda) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual: document IMAGE_BOOT_FILESMaciej Borzecki2014-09-231-0/+18
| | | | | | | | | | Document IMAGE_BOOT_FILES variable. (From yocto-docs rev: f0b5cbcde4b83911780ab525f279dcb527fb1839) Signed-off-by: Maciej Borzecki <maciej.borzecki@open-rnd.pl> Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dev-manual: Added reference to the meta-selinux layer.Scott Rifenbark2014-09-231-0/+3
| | | | | | | | | | | | Fixes [YOCTO #5482] Added a cross-reference to the meta-selinux layer in the section that describes how to make images more secure. (From yocto-docs rev: 0c96273ee857808046c5a76517c1eda4aa703c81) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Mark opkg-utils as ABISAFE for update-alternatives usageRichard Purdie2014-09-231-0/+2
| | | | | | | | | | | Currently linux-firmware rebuilds for each machine due to its usage of update-alternatives which in turn means a dependency on opkg-utils. Marking opkg-utils as ABISAFE is the only option we have right now to avoid this. (From OE-Core rev: 6829c0e161c4a8cde6624f211865922fce62d4fa) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* update-rc.d/systemd: Remove OVERRIDES dependencyRichard Purdie2014-09-232-0/+3
| | | | | | | | | | | | | Taking run-postinsts and building for two machines which have different OVERRIDES leads to two different sets of stamps for an allarch package. We don't need to depend on OVERRIDES in these classes, the end resulting variables are good enough. We can therefore exclude the dependency and allow a single package to be generated for run-postinsts. (From OE-Core rev: fdc949154e64afb41dd4db3a97be74a15963128d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Add in useradd dependencies as ABISAFE dependenciesRichard Purdie2014-09-231-0/+3
| | | | | | | | | | Currently allarch recipes using useradd rebuild each time MACHINE changes which is not desireable. Adding the useradd dependencies to this list ensures they do not change under these circumstances. (From OE-Core rev: 7743a309017f0fb9286f00b1f6f546ee95c05303) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* man: fix not support xz/bz2 compressionHongxu Jia2014-09-231-1/+2
| | | | | | | | | | | | In oe-core, bunzip and unzx located in /usr/bin/ rather than /usr, so tweak man's config. [YOCTO #6750] (From OE-Core rev: a8f07626d627b49913835778cc8039accd8b9896) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ltp: make setregid02 be able to passRoy.Li2014-09-232-0/+62
| | | | | | | | | | | | [YOCTO #6748] replace "nobody" group with "nogroup", since the user "nobody" belongs to "nogroup" group and no "nobody" group in oe-core (From OE-Core rev: 3fc1b5acb50aa864d386f69a1c0d0db0425f970c) Signed-off-by: Roy.Li <rongqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemtap: disable libvirtWenzong Fan2014-09-233-0/+43
| | | | | | | | | | | | | | | | | libvirt is automatically linked to if present, this undetermined dependency may cause build errors like: ../lib/libvirt.so: undefined reference to `libssh2_channel_open_ex' ../lib/libvirt.so: undefined reference to `libssh2_session_hostkey' ... Both libvirt and libssh2 are not oe-core recipes for now, just disable libvirt to fix this issue. (From OE-Core rev: 815b44914eb30b86dfce0e81ffda7884e0efcc34) Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* beaglebone.conf: add IMAGE_BOOT_FILESMaciej Borzecki2014-09-231-0/+2
| | | | | | | | | | | | Set IMAGE_BOOT_FILES to list of files that end up in boot partition. This in turn is used by wic to generate a bootable SD card image. (From meta-yocto rev: 4ee4785154c1702ecfb8389f3c6ab99957a2f1d0) Signed-off-by: Maciej Borzecki <maciej.borzecki@open-rnd.pl> Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic: add sdimage-bootpart kickstart fileMaciej Borzecki2014-09-231-0/+6
| | | | | | | | | | | | | | Add kickstart for generating a SD card image that should cover most use case scenarios. The layout is as follows: - 16MB vfat partition that IMAGE_BOOT_FILES will be copied to, 4k alignment - ext4 rootfs, 4k alignment (From OE-Core rev: bb01a6be7b32aa675f5003a6012a60a081212e8c) Signed-off-by: Maciej Borzecki <maciej.borzecki@open-rnd.pl> Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic: add new bootimg-partition pluginMaciej Borzecki2014-09-231-0/+108
| | | | | | | | | | | | This patch implements 'bootimg-partition source plugin class for 'wic'. The plugin creates an image of boot partition, copying over files listed in IMAGE_BOOT_FILES bitbake variable. (From OE-Core rev: 4a3200d710d953956064c28188577fbd461d093d) Signed-off-by: Maciej Borzecki <maciej.borzecki@open-rnd.pl> Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation.conf: document IMAGE_BOOT_FILESMaciej Borzecki2014-09-231-0/+1
| | | | | | | | | | Document IMAGE_BOOT_FILES variable. (From OE-Core rev: 8007f41aa824db2ee681d9dd98a0b06f44fc9d6d) Signed-off-by: Maciej Borzecki <maciej.borzecki@open-rnd.pl> Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic: set bootimg_dir when using image-name artifactsMaciej Borzecki2014-09-232-5/+11
| | | | | | | | | | | | | Running wic with -e to use artifacts from a named image, bootimg_dir was always passed as empty string to partition source plugins. The patch sets bootimg_dir to current value of DEPLOY_DIR_IMAGE, as bootloader artifacts end up in that location as well. (From OE-Core rev: d7f69e6f0932a927b6ce289fb47ba575d7aaa1c8) Signed-off-by: Maciej Borzecki <maciej.borzecki@open-rnd.pl> Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic: fix vfat partition sector count only if neededMaciej Borzecki2014-09-231-3/+5
| | | | | | | | | | | | | | VFAT rootfs partitions sector count would get updated always even if there is no need. Since parition size in wic is expressed in MB, any sub MB change will cause the generated partition image to be larger than allocated space within the disk image. Fortunately, partitions sized in MB will most of the time have a proper sector count. (From OE-Core rev: 99bee4cb489800d74dea4d2158ff834413685f04) Signed-off-by: Maciej Borzecki <maciej.borzecki@open-rnd.pl> Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic: use IMAGE_EXTRA_SPACE for vfat rootfsMaciej Borzecki2014-09-231-2/+2
| | | | | | | | | | | Functions for generating rootfs use IMAGE_EXTRA_SPACE rather than BOOTDD_EXTRA_SPACE. The latter is used in boot image source plugins. (From OE-Core rev: 44abf447f8e4ed11cbbe53a4fb0ecf10a20f0f9e) Signed-off-by: Maciej Borzecki <maciej.borzecki@open-rnd.pl> Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* wic: minor comment updateMaciej Borzecki2014-09-231-1/+1
| | | | | | | | | | Update comment about types of generated partition images. (From OE-Core rev: ba1503f77e0c03fe6c715b61983008b7a534ae20) Signed-off-by: Maciej Borzecki <maciej.borzecki@open-rnd.pl> Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative: Add uninative - a way of reusing native/cross over multiple distrosRichard Purdie2014-09-232-0/+92
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These patches are the start of a new idea, a way of allowing a single set of cross/native sstate to work over mutliple distros, even old ones. The assumption is that our own C library is basically up to date. We build and share a small tarball (~2MB) of a prebuilt copy of this along with a patchelf binary (which sadly is C++ based so libstdc++ is in there). This tarball can be generated from our usual SDK generation process through the supplied recipe, uninative-tarball. At the start of the build, if its not been extracted into the sysroot, this tarball is extracted there and configured for the specified path. When we install binaries from a "uninative" sstate feed, we change the dynamic loader to point at this dynamic loader and C librbary. This works exactly the same way as our relocatable SDK does. The only real difference is a switch to use patchelf, so even if the interpreter section is too small, it can still adjust the binary. Right now this implements a working proof of concept. If you build the tarball and place it at the head of the tree (in COREBASE), you can run a build from sstate and successfully build packages and construct images. There is some improvement needed, its hardcoded for x86_64 right now, its trivial to add 32 bit support too. The tarball isn't fetched right now, there is just a harcoded path assumption and there is no error handling. I haven't figured out the best delivery mechanism for that yet. BuildStarted is probably not the right event to hook on either. I've merged this to illustrate how with a small change, we might make the native/cross sstate much more reusable and hence improve the accessibility of lower overhead builds. With this change, its possible the Yocto Project may be able to support a configured sstate mirror out the box. This also has positive implications for our developer workflow/SDK improvements. (From OE-Core rev: e66c96ae9c7ba21ebd04a4807390f0031238a85a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2/perforce: Use replace (1 line) instead of find (3 lines)Chad Nelson2014-09-231-7/+3
| | | | | | (Bitbake rev: 5bf5a937b26896bedbfea78dd1d62bce5a26ac2a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: fetch2/perforce: Fix localfile name if labels are usedChad Nelson2014-09-231-10/+7
| | | | | | | | | | | | | | I could apply the label "release_1.0" to a super project that contains many sub projects. If my recipes have SRC_URI's that use that label but grab different sub-folders, than there's a bug where the cached localfile (tar.gz) will not be unique and reused at the wrong times. SRC_URI = "p4://perforce::1234@//depot/SuperProject/MiniProjectAAA/...;label=release_1.0 \ p4://perforce::1234@//depot/SuperProject/MiniProjectBBB/...;label=release_1.0" (Bitbake rev: 3b5b1703b77490116dda895b29737cea51a3d6a0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: knotty: Ensure commandline parameters are updated in memres serverRichard Purdie2014-09-234-0/+20
| | | | | | | | | | | | | | | | When using options like -k, -f, -v and so on with the memory resident server, they'd currently only be set on the initial values passed to the original command. This ensures they now match those specified on the commandline for the options where this makes sense. To make this work, a command to update the options on the server side is required so this is added. [YOCTO #5292] (Bitbake rev: 1c75cc4d0c8b606c1fe76e6bf60bf6a32298b105) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* irda-utils: remove inherit autotoolsRoss Burton2014-09-231-1/+1
| | | | | | | | | irda-utils doesn't use autotools, so don't inherit it. (From OE-Core rev: d5e2a59ab59e3d67d09c5f25b8623186af855e17) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-init-build-env-memres: Fix automatic port usageRichard Purdie2014-09-231-4/+4
| | | | | | | | | | | | | The use of an automatic port wasn't working correctly since the server was never getting started when port == -1. This fixes things so the server is started when port is not specified (i.e. automatic) ensuring this happens before BBSERVER is set. [YOCTO #6563] (From OE-Core rev: 982553b6d56ca4bfd095c1bcb736ae3b77deefa7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.14: update to v3.14.19Bruce Ashfield2014-09-233-16/+16
| | | | | | | | | Updating to the latest korg -stable update. (From OE-Core rev: 7212dcb3a67b9a9b844b74e997d2e3ea7902555f) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: update to v3.10.55Bruce Ashfield2014-09-233-16/+16
| | | | | | | | | Updating to the latest korg -stable update. (From OE-Core rev: 9745ffc0ae25be980d92f195937cef6d1f406ab2) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.17: bump to v3.17-rc6Bruce Ashfield2014-09-232-12/+12
| | | | | | | | | | Updating the 3.17 recipe to -rc6. This is nearly the release kernel, and should have very few changes aftert this point. (From OE-Core rev: 845e01d906982c2147828b97129e95e8a79dce7c) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.17: switch to dedicated 3.17 repositoryBruce Ashfield2014-09-231-1/+1
| | | | | | | | | | The 3.17 repository is ready, so we no longer need to reuse the linux-yocto-dev tree. (From OE-Core rev: c304674833360e0e2dceca3ebeb535025597e46f) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.17: update to v3.17-rc5Bruce Ashfield2014-09-232-12/+12
| | | | | | | | | Bumping the SRCREVs to import the latest korg -rc. (From OE-Core rev: 8ae153f7da3244c3dd24cc5dbd722af26624201b) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.14: update to v3.14.18 and -rt9Bruce Ashfield2014-09-233-16/+16
| | | | | | | | | Refreshing the 3.14 kernel to a new korg stable and -rt release. (From OE-Core rev: 91204afeb508ae21f8f2a32c340ec85efbf33fd0) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.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-18 05:47:22 +0000