summaryrefslogtreecommitdiff
path: root/meta/recipes-core
AgeCommit message (Collapse)AuthorFiles
2015-09-29util-linux: add runuser PAM config files to fix runuser errorChen Qi4
The runuser command fails with below error message, add proper PAM config files to fix the problem. The config files are borrowed from CentOS 7.0 release. runuser: Failure setting user credentials Signed-off-by: Shan Hai <shan.hai@windriver.com> Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-29systemd: add PACKAGECONFIG for qrencodeJonathan Liu1
Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-28busybox: Use CC instead of bare LD to be the LinkerKhem Raj3
This patch was on mailing list, another patch to make sure -r is not passed directly but via -Wl switch is added. This was exposed when using clang and gold linker, clang does not have -r switch to do relocatable objects and problem happens specific to OE becuase we use LD = CC now what happens is that busybox assumes that linker will be called directly, and hence sprinkles linkers options in its kbuild system which aggregate into LDFLAGS, some of these options are happily ignored by gcc as well but it passes -r options rightly to linker so it all works, however when using clang, this falls apart since -r is not known option for clang so it drops this option and all obects which should be partially linked becomes ET_EXEC and when they are added to final link then gold starts to get confused /mnt/home/kraj/work/angstrom/build/tmp-angstrom-glibc/sysroots/x86_64-linux/usr/bin/arm-angstrom-linux-gnueabi/arm-angstrom-linux-gnueabi-ld: error: applets/built-in.o: unsupported ELF file type 2 clang-3.7: error: linker command failed with exit code 1 (use -v to see invocation) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-28busybox: Use UTMPX instead of legacy UTMPKhem Raj2
This makes busybox honor UTMPX feature if available in a libc [YOCTO #8243] Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-28packagegroup-core-standalone-sdk-target: ensure libatomic is in SDKRoss Burton1
Some architectures (such as MIPS) need libatomic from gcc-runtime to perform atomic operations, so this package should be included in all SDKs. [ YOCTO #8274 ] Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-28glibc/mmc-utils: Rename 'BRANCH' variable to 'SRCBRANCH' for clearnessOtavio Salvador2
The 'BRANCH' variable name has no explicit relation with the SRC_URI. Using 'SRCBRANCH' makes it more obvious and easier to identify. This patch makes the use consistent across the metadata. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-28systemd: apply persistent storage udev rules also for /dev/hd*Patrick Ohly2
This fixes booting with initramfs and root=UUID on machines with IDE disks, like "runqemu hdddirect", and kernels which still use the deprecated CONFIG_IDE. v2: Rebased against current master-next. Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-24systemd: fix tmpfiles location when multilib in useReinette Chatre1
Systemd's configuration files for creation, deletion and cleaning of volatile and temporary files are installed in /usr/lib even when multilib is in use (when /usr/lib64 is available). In this check the systemd.conf file will not be found if libdir is /usr/lib64 so we fix the path to match this file's installation path to look for it in ${exec_prefix}/lib Signed-off-by: Reinette Chatre <reinette.chatre@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-24systemd: disable problematic GCC 5.2 optimizationsJonathan Liu1
This fixes systemd failing to start on Raspberry Pi 2 if it is compiled with GCC 5.2. It would try to start "Journal Service" and "udev Kernel Device Manager" but fail repeatedly. [YOCTO #8291] Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-24Revert "systemd: disable problematic GCC 5.2 optimizations"Ross Burton1
This reverts commit d347bd8b672fbd614a6267f640133cf399b9645f. Accidentally merged v1 of this, revert so we can merge v2. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-21systemd: disable problematic GCC 5.2 optimizationsJonathan Liu1
This fixes systemd failing to start on Raspberry Pi 2 if it is compiled with GCC 5.2. It would try to start "Journal Service" and "udev Kernel Device Manager" but fail repeatedly. [YOCTO #8291] Signed-off-by: Jonathan Liu <net147@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-21initramfs-framework: better error reporting for invalid root boot parameterPatrick Ohly1
When the "boot" parameter refers to a non-existent device, the only visible output at normal log levels was a rather confusing: ERROR: There's no '/dev' on rootfs. That's because the actual error, not being able to find the root device, was only a debug message, which gets ignored in the default mode. Promoting the "root '$bootparam_root' doesn't exist." message from "debug" to "msg" gives sufficient context to understand the error. A more intrusive change would be to change also the control flow. Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-21initramfs-framework: fix "support dropping into shell on failure"Patrick Ohly1
Due to a missing $ before the variable name, all fatal errors ended up invoking a shell, instead of only doing that when init_fatal_sh is set as boot parameter. Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-16glibc: Ensure OVERRIDES doesn't influence sstate checksumRichard Purdie1
Switching MACHINE was causing nativesdk-glibc to rebuild. This was from the use of OVERRIDES in one of the functions. Exclude OVERRIDES from the checksum to avoid this. [patch to oe-selftest to ensure this doesn't regress follows] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-16systemd: fix missing space in SRC_URI appendMartin Jansa1
* it was introduced in: commit 5196d7bacaef1076c361adaa2867be31759c1b52 Author: Aníbal Limón <anibal.limon@linux.intel.com> Date: Fri Aug 28 11:15:01 2015 -0500 Subject: systemd: Increase devices timeout in QEMU machines to avoid failures on serial-getty Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-16glibc: don't require bash for nscd init scriptRoss Burton2
The nscd init script uses #! /bin/bash but only really uses one bashism (translated strings), so remove them and switch the shell to #! /bin/sh. Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-15init-install-efi.sh: Avoid /mnt/mtab creation if already presentLeonardo Sandoval1
The base-files recipe installs /mnt/mtab (it is a softlink of /proc/mounts), so if an image includes the latter, there is no new to created it again inside the install-efi.sh script, otherwise an error may occur as indicated on the bug's site. [YOCTO #7971] Signed-off-by: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-14midori: remove the recipe and replace references to midori with epiphanyAlexander Kanavin1
(From OE-Core rev: b7e14c77ffb3d994d59ddc076d7e0263f39546c1) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-12meta: Fix Upstream-Status statementsRoss Burton9
Fix a variety of problems such as typos, bad punctuations, or incorrect Upstream-Status values. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-12initramfs-framework: support dropping into shell on failurePatrick Ohly1
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... Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-12initramfs-framework: support init boot parameterPatrick Ohly1
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. Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-12initramfs-framework: support ro boot parameterPatrick Ohly1
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. Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-12initramfs-framework: support rootflags and rootfstype boot parameterPatrick Ohly1
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()])}" Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-12packagegroup-core-nfs: provide the nfs-client IMAGE_FEATURESRoy Li2
provide the nfs-client IMAGE_FEATURES, to ease a user to only install nfs client related files to image Signed-off-by: Roy Li <rongqing.li@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-09-11systemd: Implement OE-Specific systemd-sysv-installKhem Raj2
Support for chkconfig (--enable-chkconfig) was removed in favour of calling an abstraction /lib/systemd/systemd-sysv-install. This needs to be implemented for OE. Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-11systemd: Upgrade 219 -> 225Khem Raj12
Drop patches that were straight backports from upstream MIT licence was unused and dropped from systemd sources for more details see https://github.com/systemd/systemd/commit/8f1e0c5f38cdf7e401ab4d2bb93ad816d08e7715 Drop gtkdoc dependency since libudev API documentation has been converted from gtkdoc into man pages Remove packaging gudev as it has moved to separate repository outside systemd For more details see https://github.com/systemd/systemd/commit/2375607039517c88df51ef16ddbb624ec1c10654 package newly added script for xorg to be usable with systemd --user intance For more details see https://github.com/systemd/systemd/commit/1401ec2d34bcde406ced531a72dc46ebaf332594 machinectl now has shell support private-zone DHCP options are supported by systemd-networkd For complete differences between two releases run git log --oneline v219..v225 in systemd git clone Change-Id: I998e652382950a3c74c4839f3767ef8bef23d88f Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-07busybox: Enable getopt appletKhem Raj2
getopts is a common applet more so now needed by systemd for working with sysv scripts Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-06initramfs-framework: handle kernel parameters with . insidePatrick Ohly1
Kernel parameters like "uvesafb.mode_option=640x480-32" were turned into shell variables named "bootparam_uvesafb.mode_option", which triggered errors from the shell because the name is not valid. Now points get replaced with underscores, leading to bootparam_uvesafb_mode_option in this example. Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-06initramfs-live-boot: create /dev/consolePatrick Ohly1
Some kernels, for example linux-yocto 3.19 for qemux86, fail to execute /init in an initramfs unless there is already a /dev/console char device in the initramfs. Booting then fails with: Kernel panic - not syncing: /dev/console is missing or not a character device! Please ensure your rootfs is properly configured The panic itself comes from a linux-yocto specific patch to kernel_init_freeable in init/main.c, but even without it, that function will print an error when /dev/console is missing. The kernel's Documentation/initrd.txt also mentions creating that device. It remained unclear why this is not a problem on other machines. On intel-corei7-64 from meta-intel, something (the kernel?) creates /dev/console and /dev/[012] before transfering control to the init script. In that case, creating /dev/console in advance is not necessary, but does not cause any problem either. Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-06initramfs-framework: create /dev/consolePatrick Ohly1
Some kernels, for example linux-yocto 3.19 for qemux86, fail to execute /init in an initramfs unless there is already a /dev/console char device in the initramfs. Booting then fails with: Kernel panic - not syncing: /dev/console is missing or not a character device! Please ensure your rootfs is properly configured The panic itself comes from a linux-yocto specific patch to kernel_init_freeable in init/main.c, but even without it, that function will print an error when /dev/console is missing. The kernel's Documentation/initrd.txt also mentions creating that device. It remained unclear why this is not a problem on other machines. On intel-corei7-64 from meta-intel, something (the kernel?) creates /dev/console and /dev/[012] before transfering control to the init script. In that case, creating /dev/console in advance is not necessary, but does not cause any problem either. Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-06systemd: remove hard-coded paths in FILES entriesJoshua Lock1
Signed-off-by: Joshua Lock <joshua.lock@collabora.co.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-06busybox: fixes for when base_bindir != /binJoshua Lock1
* Replace all hard-coded paths with variables * Run sed over busybox.links.* to replace /bin with ${base_bindir} Signed-off-by: Joshua Lock <joshua.lock@collabora.co.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-03ifupdown: create alternative linksJoe Slater1
Inherit update-alternatives so links are created. ifup and ifdown are higher priority than the versions provided by busybox. Signed-off-by: Joe Slater <jslater@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-03ifupdown: import recipeJoe Slater4
Implements ifup and ifdown. Copied from https://github.com/WindRiver-OpenSourceLabs/meta-overc.git as of commit aa89eebffe06e4aa04701eae9691cb3049cbaef9. Signed-off-by: Joe Slater <jslater@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-01os-release: add the public package-signing keyMarkus Lehtonen1
Adds the public package-signing key into this package. It will be installed under /etc/pki/rpm-gpg if the RPM signing feature is used. The key file is not currently directly used by anything in the target system. It is merely there for possible later use. [YOCTO #8134] Signed-off-by: Markus Lehtonen <markus.lehtonen@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-01glibc: package nscd related filesRoy Li2
install nscd related configuration file, startup files, and package them, make nscd easy to startup Signed-off-by: Roy Li <rongqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-31dropbear: update to 2015.68Alexander Kanavin3
LICENSE checksum has changed because the copyright year was changed from 2014 to 2015 in it: https://github.com/mkj/dropbear/commit/19e1afbd1ca6d306166ce74bcd6c6889f8d196f3 Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-31upstream_tracking.inc: deprecate and move contents to recipesAlexander Kanavin1
No-update reasons and manual version checks should be in the recipes themselves because otherwise they're prone to getting out of date. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-31packagegroup-base: pull in iw as well as wireless-toolsChristopher Larson1
As was discussed in the commit which adds iw: iw uses cfg80211/nl80211, which is the way of the future. wireless-tools uses WEXT, which uses ioctl, which is in deep maintenance mode. See http://wireless.kernel.org/en/developers/Documentation/Wireless-Extensions. Also https://wireless.wiki.kernel.org/en/users/Documentation/iw indicates "The old tool iwconfing, which uses Wireless Extensions interface, is deprecated and it's strongly recommended to switch to iw and nl80211." wireless-tools is kept as well for now for compatibility reasons, until we have verified that all the network configuration mechanisms are using iw. This adds VIRTUAL-RUNTIME_wireless-tools as a distro convenience. Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-30os-release: Exclude DATETIME from sstate signatureRichard Purdie1
I'm torn over this, I can see someone wanting this to vary in each build. What pushed me to believe its incorrect in its current form is that it changes for every MACHINE build, making a complete mess if you try and generate package feeds using it. The alternative would be to give up on allarch in this case and make it MACHINE specific which at least would then be more consistent when the package makes it to a package feed. If someone wants to do that, the can propose another patch but this change at least make package feed usage 'sane' again and avoids the perpetual rebuilds. Incidentally, its worth noting that changes in source metadata revision used for the build and included in this recipe would still trigger rebuilds which is likely the common use case people actually care about. (From OE-Core rev: 46de6f6eb9c4387298fafb48fb9c36abc3ff48a4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-30jpeg: update to version 9aAlexander Kanavin3
Previous webkit version was blocking this; latest webkit works fine. (From OE-Core rev: 5d9d179023857c53801e24b18f9b3051d9c84145) 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>
2015-08-30systemd: Cache/define tool paths for targetKhem Raj1
Recently, systemd has added a patch f00929ad622c978f8ad83590a15a765b4beecac9 where it now pokes at the system to find out the path of mount/umount tools, this caused the builds to fail because it ended up with identifying these programs from native sysroot but they were actually meant for target, this lead to boot failures due to none of mount worked because the paths are encoded into systemd binaries during build time. Correct few others while here, these are not yet detected wrongly in my build, because those binaries are not found in my native sysroot but if some one staged the native providers of these packages they will fail too. (From OE-Core rev: 9d87fbc87276673d958a65d476d06fec96add8e7) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-30core-image-minimal: Add 4M extra space when using systemdKhem Raj1
qemu images fail to rebuild the hwdb due to no space letf on device systemd-hwdb-update.service - Rebuild Hardware Database Loaded: loaded (/lib/systemd/system/systemd-hwdb-update.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2015-08-15 21:39:28 UTC; 28s ago Docs: man:hwdb(7) man:systemd-hwdb(8) Process: 92 ExecStart=/bin/systemd-hwdb update (code=exited, status=1/FAILURE) Main PID: 92 (code=exited, status=1/FAILURE) Aug 15 21:39:28 qemux86 systemd-hwdb[92]: Failure writing database //etc/udev/hwdb.bin: No space left on device Aug 15 21:39:28 qemux86 systemd[1]: systemd-hwdb-update.service: Main process exited, code=exited, status=1/FAILURE Aug 15 21:39:28 qemux86 systemd[1]: Failed to start Rebuild Hardware Database. (From OE-Core rev: 4086c539d47bc837e775972016e1844a3676c8e7) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-30systemd: Remove exporting special CPPKhem Raj1
This is no more needed. it was done long ago while systemd lived in meta-openembedded http://lists.openembedded.org/pipermail/openembedded-commits/2012-August/141061.html The accompanying patch has been applied to systemd already so we were not needing to set CPP for sometime now. as a nice side effect it helps compiling systemd with clang (From OE-Core rev: b816e3f520bf71c9b681ccea30c8eefd62fb20a2) 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>
2015-08-30psplash: Turn psplash_fb_plot_pixel() into static inlineKhem Raj2
This function is not used anywhere except psplash-fb.c so make it static inline function which is portable across compilers Fixes issues like psplash-fb.o: In function `psplash_fb_draw_rect': | /mnt/home/kraj/work/angstrom/sources/openembedded-core/build/tmp-glibc/work/i586-oe-linux/psplash/0.1+gitAUTOINC+14c8f7b705-r15/git/psplash-fb.c:363: undefined reference to `psplash_fb_plot_pixel' (From OE-Core rev: 2429932c2dc1f81bf04f4377911094e2c8a04a19) 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>
2015-08-30sysvinit: Fix makefile bug found with clangKhem Raj2
This is due to specifying .h files on linker cmdline clang driver is picky about it, and its not entirely correct either (From OE-Core rev: de45b5e68faeefe3d68818d456f280b98f397634) 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>
2015-08-29systemd: Increase devices timeout in QEMU machines to avoid failures on ↵Aníbal Limón2
serial-getty Systemd serial-getty is failing because dev-tty ends with timeout, systemd uses a default timeout of 90 secs that it's reached on AB's production environment due to high I/O loads (nfs). When use QEMU is used without KVM support, the machine code is executed by TCG (software code execution) that is dependent on devices layer and causes locks between TCG/Devices increasing the machine code execution time [1]. QEMU don't support configuration of device timeout always uses a default one that is 90 secs, so the next patch increases the device timeout to 240 secs [2] in order give enough time to get devices ready. It ONLY applies on QEMU machines. [YOCTO #8141] [1] http://blog.vmsplice.net/2011/03/qemu-internals-overall-architecture-and.html [2] https://bugzilla.yoctoproject.org/show_bug.cgi?id=8141#c10 Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-29sysvinit-inittab: Run ttys on ttys that don't have tty in the nameRandy Witt1
On qemuarm64 the second serial port in SERIAL_CONSOLES will be hvc0. Since that doesn't have tty in the name, a correct label didn't get added to inittab. This change makes both names with tty and without work. Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-08-24glib: add a warning suppression patch to glibAlexander Kanavin2
Otherwise QA check will fail. Some schemas in gsettings-desktop-schemas (such as proxy and locale) are still using deprecated paths, as of 3.16.1. This causes warning messages, and meta/lib/oe/rootfs.py complaints about them. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
2015-08-24classes/gnomebase: change tarball compression to xzAlexander Kanavin1
Upstream, xz has been the only format for some time now, so let's make it the default and adjust recipes that package old stuff. Signed-off-by: Alexander Kanavin <alexander.kanavin@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-10 10:54:26 +0000