summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFiles
2014-10-30autotools: Use make clean for builds not supporting B != SRichard Purdie1
If the build doesn't support B != S, we can try running "make clean" instead to try and clean up previous objects if the hash for the task has changed. This tries to ensure that when variables like ${baselib} change, the changes are correctly accounted for. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-10-30wic: Update bootimg-partition to use bootimg_dirTom Zanussi1
Update bootimg-partition to use bootimg_dir instead of img_deploy_dir, to match similar usage in other plugins. As mentioned elsewhere, plugins should use the passed-in value for bootimg_dir directly if non-null, which corresponds to a user-assigned value specified via a -b command-line param, and only fetch the value from bitbake if that value is null. Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-10-30wic: Remove special-case bootimg_dirTom Zanussi7
The first iterations of wic very shortsightedly catered to two specific use-cases and added special-purpose params for those cases so that they could be directly given their corresponding boot artifacts. (hdddir and staging_data_dir). As more use-cases are added, it becomes rather obvious that such a scheme doens't scale, and additionally causes confusion for plugin writers. This removes those special cases and states explicitly in the help text that plugins are responsible for locating their own boot artifacts. Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-10-30Revert "wic: set bootimg_dir when using image-name artifacts"Tom Zanussi2
This reverts commit 7ce1dc13f91df70e8a2f420e7c3eba51cbc4bd48. This patch broke the assumption that a non-null boot_dir means a user-assigned (-b command-line param) value. Reverting doesn't break anything, since the case it was added for doesn't use the boot_dir for anything except debugging anyhow. Fixes [YOCTO #6290] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-10-30wic: Update the help text to include -D (--debug)Tom Zanussi1
The --debug option is missing from the wic help text; this adds it and at the same time rearranges the usage into a more logical arrangement. Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-10-30wic: Use overhead factor when creating partitions from rootfs directoriesTom Zanussi2
When creating partitions sized to given rootfs directories, filesystem creation could fail in cases where the calculated target partition size was too small to contain the filesystem created using mkfs. This occurred in particular when creating partitions to contain very large filesystems such as those containing sdk image artifacts. This same limition is present in the oe-core image creation classes, which can be readily see by changing IMAGE_OVERHEAD_FACTOR from the default 1.3 to 1.0 and building a sato-sdk image. It should be possible to calculate required sizes exactly given the source rootfs and target filesystem types, but for now, to address the specific problem users are hitting in such situations, we'll just do exactly what oe-core does and define and use an IMAGE_OVERHEAD_FACTOR or 1.3 in those cases. Fixes [YOCTO #6863]. Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-10-30wic: Don't allow mkfs to fail silently in partition commandTom Zanussi1
The return code from the mkfs command used by the partition creation command was being ignored, allowing it to silently fail and leaving users mystified as to why the resulting filesystem was corrupted. This became obvious when failures occurred when creating large e.g. sdk filesystems [YOCTO #6863]. Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-10-30image.py: Fix error in graph sortingPascal Bach1
The graph sorting algorithm for image dependencies does a look for an occurrence of a searched string instead of comparing the chunk to the searched string. This leads to the problem that ubifs is recognized as ubi aswell. This fixes this by splitting up the string into chunks. Signed-off-by: Pascal Bach <pascal.bach@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-10-30multilib.conf: set MULTILIB_GLOBAL_VARIANTS conditionallyPeter Seebach1
It is not entirely obvious that all reasonable configurations will have multilib.conf strictly before the file which might want to set MULTILIB_GLOBAL_VARIANTS. The x86-ish values here look like reasonable default guesses, but shouldn't override an explicit setting. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-10-30mklibs: Fix loader for mipselKhem Raj3
Additionally treat ld.so to be searched in sysroot Change-Id: I8b4acb821d9855a1163c7149bc8e369c7c438856 Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-10-30glibc: Delete ldconfig when USE_LDCONFIG is not setKhem Raj1
This avoids below QA error/warning /sbin/ldconfig [installed-vs-shipped] Change-Id: I028b692eefeaa6e0e0e6507ab4108caa29e41e91 Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-10-24rm_work: Speed up rootfs/populate_sdk removalRichard Purdie1
Commands like bitbake X -c rootfs or bitbake X -c populate_sdk do not trigger rm_work to clean up the directories afterwards since it traditionally hooks onto do_build. This change means those two tasks now clean up after themselves. We use the cleandirs function attribute to handle this. [YOCTO #6413] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-10-24gcc: poison default sysroot pathRichard Purdie6
Various pieces of the code assume that the --sysroot option gets passed into the compiler tools. By having a "sane" default, we don't always spot when this occurs and this can later show up as breakage in sstate, or in usage of the external toolchain. We've long since talked about poisoning the default such that it will break unless the correct option is specified. This patch does just that. If this patch causes something to fail to build, it most likely means the various compiler flags and commands are not correctly being passed through to the underlying piece of software and that there is a real problem that needs fixing, its not the fault of this patch. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-10-24nativesdk-cmake: Adjust toolchain paths dynamicallyOtavio Salvador3
This patch adds a flexible way to configure the CMake in SDKs. It adds a toolchain configuration script which supports subscripts for extensions, as for example Qt5. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-10-24local.conf.sample.extended: update for RPM_PREFER_ELF_ARCHRobert Yang1
Updated as the rpm upstream suggested: - RPM_PREFER_COLOR -> RPM_PREFER_ELF_ARCH - 3 -> 4 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>
2014-10-24kernel-yocto: fix branch validation for AUTOREV, non machine_meta kernelsBruce Ashfield1
The simplication of do_validate_branches missed a case where a custom kernel can supply SRCREV="${AUTOREV}", and not use SRCREV_machine at all. In this case, we will incorrectly try and test the tree for a non-existent commit, and break the build. By simplying the condition of the check to look for an empty SRCREV_machine, we can skip manipulating the tree and testing for a SRCREV. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-24linux-yocto/3.17: v3.17 release and configBruce Ashfield2
Updating the SRCREVs to incoroprate the full 3.17 release, and also updating the meta data to match the v3.17 content: 9ba007f8d0ab meta: bump kver to v3.17-final 5c6c5fe9b0bf config: remove CONFIG_HOTPLUG 0ceecad5f15a qemu: explicitly include usb configuration fragments f6c78ada8655 gfx: convert CONFIG_TABLET_USB_WACOM to CONFIG_HID_USB_WACOM cd1dbedfa3c9 x86: Support 32 bit binaries Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-24linux-yocto/3.10: 8250/8250_dw: fix compile failure due to stable/Yocto conflictBruce Ashfield3
Updating the SRCREVs for the following fix: 8250/8250_dw: fix compile failure due to stable/Yocto conflict As of merge 60a9d9fc565e4503dbb8705803e83d906afc4ad2, "Merge tag 'v3.10.48' into standard/base" the 8250_dw.c fails to compile due to an undeclared variable. This happens because stable brought in: ------------------------- commit 6d5e79331417886196cb3a733bdb6645ba85bc42 Author: Tim Kryger <tim.kryger@linaro.org> Date: Tue Oct 1 10:18:08 2013 -0700 serial: 8250_dw: Improve unwritable LCR workaround commit c49436b657d0a56a6ad90d14a7c3041add7cf64d upstream. [...] [wangnan: backport to 3.10.43: - adjust context - remove unneeded local var] Signed-off-by: Wang Nan <wangnan0@huawei.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> ------------------------ ...which deletes the p->private_data declaration since it became unused at that point, however in Yocto, we also have this: ----------------------- commit 0e02b050c3cafbcbf9952125089a27e02d6ecea9 Author: David Daney <david.daney@cavium.com> Date: Wed Jun 19 20:37:27 2013 +0000 tty/8250_dw: Add support for OCTEON UARTS. [...] Signed-off-by: Ralf Baechle <ralf@linux-mips.org> (cherry picked from commit d5f1af7ece96cf52e0b110c72210ac15c2f65438) Signed-off-by: Darren Hart <dvhart@linux.intel.com> ----------------------- ...which _adds_ another user of the p->private_data. Here we restore the declaration in order that 8250_dw compiles. Signed-off-by: Ong Boon Leong <boon.leong.ong@intel.com> [PG: add root cause info to commit log.] Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-24unifdef: remove fork, package upstreamRoss Burton3
Instead of building specifiaclly for native a static fork of unifdef from 2007, simply package the latest tarball. Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-24native.bbclass: use BUILD_* variablesRoss Burton2
Instead of replicating the logic for the host compiler naming from bitbake.conf, use the BUILD_* variables directly. Also change BUILD_CPP to use gcc -E (which native.bbclass previously used), as some recipes (e.g. grub-efi) use ${CPP} with multiple input files, which gcc -E can handle but cpp can't. Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-24rpm: realpath is required before expanding _dbpath in chrootMing Liu3
A regression is introduced by commit 66573093: [ rpm: Fix rpm relocation macro usage ] _usr turned out to be a relative path to support dyanmic config after that, but it's being used somewhere as a indicator to locate substrings, so we must get the real path of it in advance. Signed-off-by: Ming Liu <ming.liu@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-24kernel.bbclass: Create modules directory even if there is no modules installedHe Zhe1
During kernel_do_install it needs to make symbol link at ${D}/lib/modules/${KERNEL_VERSION}/build, but there will not be ${D}/lib/modules/${KERNEL_VERSION} if there is no modules installed for current image, which will result in a build failure. Add "mkdir -p ${D}/lib/modules/${KERNEL_VERSION}" here to avoid this failure and the need of similar changes in other scripts that also expect it to exist. Signed-off-by: He Zhe <zhe.he@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-24libxml2: fix CVE-2014-3660Joe MacDonald2
It was discovered that the patch for CVE-2014-0191 for libxml2 is incomplete. It is still possible to have libxml2 incorrectly perform entity substituton even when the application using libxml2 explicitly disables the feature. This can allow a remote denial-of-service attack on systems with libxml2 prior to 2.9.2. References: http://www.openwall.com/lists/oss-security/2014/10/17/7 https://www.ncsc.nl/actueel/nieuwsberichten/kwetsbaarheid-ontdekt-in-libxml2.html Signed-off-by: Joe MacDonald <joe_macdonald@mentor.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-24nfs-utils: fix start-statdRoy.Li2
1. add /bin to PATH of start-statd, otherwise systemctl can not be found. 2. drop error when systemd fails to start statd.service; since if it failed, rpc.statd will be called directly. Signed-off-by: Roy.Li <rongqing.li@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-24cross-localedef-native: provide SRCREV_FORMATJoe Slater1
Add SRCREV_FORMAT to provide a composite version number for get_srcrev() in fetch2 code. Signed-off-by: Joe Slater <jslater@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-24archiver: fix truncation of src_revJoe Slater1
In trying to eliminate AUTOINC+ from revision strings, we accidently truncated the strings to almost guarantee information from SRCREV_FORMAT, when supplied, would be lost. So, we now only delete any AUTOINC+'s from the string. Signed-off-by: Joe Slater <jslater@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-24libaio: fix for mips64Jianchuan Wang2
Add mips64 support in the libaio.h - add macro PADDED/PADDEDptr/PADDEDul in the mips64 for structure iocb to be matched userland with kernel Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-24systemd: fix libidn floating dependencyChen Qi1
WARNING: QA Issue: systemd rdepends on libidn, but it isn't a build dependency? [build-deps] Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-24grub: add cmdpath to grub configuration fileArindam Nath1
An issue was found where when yocto is installed to a hard disk from a live USB key, no matter what boot order was selected in the BIOS menu, the grub menu of the USB key would always show up. The issue was narrowed down to the way grub configuration file gets embedded into the standalone bootx64.efi image. The commit prepends ($cmdpath) to the search path for grub.cfg, thus making sure the UEFI environment itself sets this to the correct device path. This in-turn lets the grub.cfg of the boot device to be loaded. Signed-off-by: Arindam Nath <arindam.nath@amd.com> Reviewed-by: Drew Moseley <drew_moseley@mentor.com> Tested-by: Ravikiran Polepalli <Ravikiran_Polepalli@mentor.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-24spdx.bbclass: improved stability, fixed SPDX compliance issues. Changes are ↵Tobias Olausson2
reflected in licenses.conf. The previous version could crash on dead links in the rootfs, or if the manifest directory did not exist. The generated files were also not compliant with the SPDX specification, for example file entries did not always start with the FileName tag, time stamps were incorrectly formatted etc. Stability issues are addressed by added checks, originally written by Johan Thelin <johan.thelin@pelagicore.com>, who never upstreamed them. I've also added an option for getting full SPDX output from FOSSology, i.e. not only for all files, but for the package as well, including license references. License refs are required in order to process the output by SPDXTools. For that reason, this option defaults to true. Signed-off-by: Tobias Olausson <tobias.olausson@pelagicore.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-24default-versions.inc: match version of db and db-native while "AGPL-3.0" in ↵Hongxu Jia1
${INCOMPATIBLE_LICENSE} The db 6.0.30's LICENSE is 'AGPL-3.0', and db 5.3.28 LICENSE is 'Sleepycat' While building rpm image with "AGPL-3.0" in ${INCOMPATIBLE_LICENSE}, db 6.0.30 and db-native 5.3.28 were built, the different versions caused the rpm doesn't work on target. ... root@qemux86-64:~# rpm -qa |rpmdb: BDB2531 Unacceptable log file /var/lib/rpm/./log/log.0000000001: unsupported log version 21 |rpmdb: BDB2527 Invalid log file: log.0000000001: Invalid argument |rpmdb: BDB0061 PANIC: Invalid argument |==> rpmdbe_event_notify(0x623f40, PANIC(0), 0x7fffee0fbc0c) app_private (nil) |rpmdb: BDB1546 unable to join the environment |error: db_init:tmp/work/core2-64-poky-linux/rpm/5.4.14-r0/rpm-5.4.14/ rpmdb/db3.c:1144: dbenv->open(-30973): BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery ... [YOCTO #6858] Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-24libtool: Extend fix-final-rpath.patchRandy Witt1
When building upower from meta-oe, the following QA error occurred: ERROR: QA Issue: package upower contains bad RPATH It appears to have been caused by one of the cases fix-final-rpath.patch is meant to address but missed. So this change fixes the additional case that was causing upower to have the QA error. Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-24liburcu: revert ARM GCC blacklist commitJonathan Liu2
This fixes the following error when building liburcu: "Your gcc version produces clobbered frame accesses" OE-Core is using a patched GCC 4.8.2 which is able to compile liburcu properly. Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-24nfs-utils: fix a Gcc undefined behaviorRoy Li2
Calling strncpy with NULL second argument, even when the size is 0, is undefined behavior, which leads to GCC to drop the check old variable with NULL in following code. https://bugzilla.yoctoproject.org/show_bug.cgi?id=6743 Signed-off-by: Roy Li <rongqing.li@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-24python-smartpm: Add checking for "rpm-ignoresize" optionChong Lu3
The do_rootfs takes a very long time when build host has mounted many NFS devices. syscall lstat() was being called on every filesystem mounted on the build host during building. The reason for the lstat() is that rpm is verifying that enough free disk space is available to do the install. However, since the install is into the target rootfs it should not matter how much free space there is in the host mounts. Add checking for "rpm-ignoresize", by it, smart can make whether RPM skip checking for diskspace when install a rpm package. Signed-off-by: Chong Lu <Chong.Lu@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-24systemd: Use ${ROOT_HOME} instead of /rootDan McGregor2
systemd avoids using nss lookups for the root user, so naturally it assumes that root's home directory is /root. In OE that's not the case, and it can lead to long delays when shutting down due to user shutdown unit failures. Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-18build-appliance-image: Update to dizzy head revisionRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2014-10-18gst-ffmpeg: Security Advisory - ffmpeg - CVE-2013-0869Yue Tao2
The field_end function in libavcodec/h264.c in FFmpeg before 1.1.2 allows remote attackers to have an unspecified impact via crafted H.264 data, related to an SPS and slice mismatch and an out-of-bounds array access. http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-0869 Signed-off-by: Yue Tao <Yue.Tao@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-18gst-ffmpeg: Security Advisory - ffmpeg - CVE-2013-4358Yue Tao2
libavcodec/h264.c in FFmpeg before 0.11.4 allows remote attackers to cause a denial of service (crash) via vectors related to alternating bit depths in H.264 data. http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-4358 Signed-off-by: Yue Tao <Yue.Tao@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-18mtools: fix broken /usr/bin/lzWenlin Kang2
When build fs with mtools-3.9.9, has file /usr/bin/lz in rootfs, it is the symlink to uz: root@qemu3:~# /usr/bin/lz -sh: /usr/bin/lz: No such file or directory $root@qemu3:~# ls -l /usr/bin/lz lrwxrwxrwx 1 root root 2 Jul 18 18:07 /usr/bin/lz -> uz root@qemu3:~# uz -sh: uz: command not found But the uz isn't actually exist, so the result is that lz is a broken symlink. The root cause is that uz hasn't been installed when install-scripts. Signed-off-by: Wenlin Kang <wenlin.kang@windriver.com> Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
2014-10-18gnupg_1.4.7: add package config libusbKai Kang1
If build gnupg 1.4.7 after libusb-compat, it shows warning: WARNING: QA Issue: gnupg rdepends on libusb-compat, but it isn't a build dependency? [build-deps] Add package config libusb to fix it. Signed-off-by: Kai Kang <kai.kang@windriver.com>
2014-10-18openssl: upgrade to 1.0.1jRoss Burton1
Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-18readline: Security Advisory - readline - CVE-2014-2524Kai Kang2
The _rl_tropen function in util.c in GNU readline before 6.3 patch 3 allows local users to create or overwrite arbitrary files via a symlink attack on a /var/tmp/rltrace.[PID] file. http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-2524 Signed-off-by: Yue Tao <Yue.Tao@windriver.com> Signed-off-by: Kai Kang <kai.kang@windriver.com>
2014-10-18gnupg: CVE-2013-4242Kai Kang2
GnuPG before 1.4.14, and Libgcrypt before 1.5.3 as used in GnuPG 2.0.x and possibly other products, allows local users to obtain private RSA keys via a cache side-channel attack involving the L3 cache, aka Flush+Reload. Patch from commit e2202ff2b704623efc6277fb5256e4e15bac5676 in git://git.gnupg.org/libgcrypt.git Signed-off-by: Yong Zhang <yong.zhang@windriver.com> Signed-off-by: Kai Kang <kai.kang@windriver.com>
2014-10-18sstate.bbclass: Fix up white space lost in last commit.Peter Urbanec1
Commit e9672387 split one long line into a multi-line string, but in the process white space between words was lost. This results in badly formatted output when this message is printed. Signed-off-by: Peter Urbanec <openembedded-devel@urbanec.net>
2014-10-18sstate.bbclass: specify func dirs for sstate_hardcode_pathWenzong Fan1
For some recipes that inhrient cmake, the ${B} may be removed by cmake_do_configure() while sstate_hardcode_path() running, this causes build errors: Exception: OSError: [Errno 2] No such file or directory: \ '/path/to/build' The function sstate_hardcode_path() called command: $SSTATE_SCAN_CMD which extended as "find ${SSTATE_BUILDDIR} ..." So the proper function dirs could be ${SSTATE_BUILDDIR}. Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-18file: add wrapper to nativesdk-fileHongxu Jia1
"file" command in exported SDK doesn't work: ... $ file sysroots/ file: could not find any valid magic files! ... In oe-core commit 68d548cbae729eaea8ce1403dc95ff63c4a7375c, it added wrapper to file-native. Do the same thing for nativesdk-file. Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-18openssh: avoid screen sessions being killed on disconnect with systemdPaul Eggleton1
Tell systemd just to kill the sshd process when the ssh connection drops instead of the entire cgroup for sshd, so that any screen sessions (and more to the point, processes within them) do not get killed. (This is what the Fedora sshd service file does, and what we're already doing in the dropbear service file). Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-18python: force off_t size to 8 to enable large file supportPaul Eggleton1
If DISTRO_FEATURES contains "largefile", force the size of off_t to 8 as a workaround for having ac_cv_sizeof_off_t=4 on 32-bit systems. In future we will likely drop the value from the site file, but for now this is a slightly safer fix. Fixes [YOCTO #6813]. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2014-10-18wic/bootimg-pcbios.py: checking the existance of syslinuxHongxu Jia1
While syslinux not existed in $bootimg_dir, there was a error: $ wic create directdisk -e core-image-minimal ... |Creating image(s)... |Error: exec_cmd: install -m 444 /home/jiahongxu/yocto/ build-20141010-yocto/tmp/deploy/images/qemux86-64/syslinux/ ldlinux.sys /var/tmp/wic/build/hdd/boot/ldlinux.sys returned '1' instead of 0 ... Add checking for the existance of syslinux to fix this issue. If syslinux didn't exist in anywhere, prompt user to build it. [YOCTO #6826] Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
generated by cgit v1.2.3 (git 2.25.1) at 2025-03-06 20:43:09 +0000