summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* init-install.sh: add support for installing initramfs onto the targetChenQi/initramfs-uuidChen Qi2014-06-161-9/+40
| | | | | | | | | | Add support to install initramfs image or the kernel bundled with it onto the target. And if there's an initramfs image available, we try to use the 'root=UUID=xxx' in the grub entry so that the target can always boot up even if the device names are changed, say, from /dev/hdb to /dev/hda. Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
* busybox: enable uuid support by defaultChen Qi2014-06-161-19/+19
| | | | | | | | | | | | This patch enables several configuration items to enable UUID support by default. This makes busybox's `mount' able to deal with /etc/fstab with lines such as "UUID=xxx / ext4 defaults 0 1". The CONFIG_FEATURE_VOLUMEID_XXX configuration items need to be enabled, otherwise, the `mount' command from busybox cannot get UUID of the corresponding filesystems. Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
* initramfs-live-install: rdepend on util-linux-blkidChen Qi2014-06-161-1/+1
| | | | | | | We need the blkid command from util-linux-blkid package to get the UUID of a particular partition. Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
* bootimg.bbclass: take initramfs into considerationChen Qi2014-06-161-1/+6
| | | | | | | | | | | It's a reasonable assumption that if INITRAMFS_IMAGE is set, the user wants to do something with it. So the bootimg.bbclass should not just ignore the existence of INITRAMFS_IMAGE. This patch fixes the bootimg.bbclass to ship the initramfs image or the bundled kernel for later use. Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
* kernel.bbclass: also install the bundled kernel to STAGING_KERNEL_DIRChen Qi2014-06-161-0/+1
| | | | | | | | | | Storing the bundled kernel in ${D} would have the risk of getting deleted by rm_work. It also makes the bundled kernel unavailable to others until the kernel is deployed. So it's better to also install the bundled kernel into ${STAGING_KERNEL_DIR} so that others could use it once do_bundle_initramfs is finished. Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
* initramfs-framework: fix an error in finish moduleChen Qi2014-06-161-3/+1
| | | | | | | | It's possible that the /dev directory doesn't exist under $ROOTFS_DIR. This should not suggest any invalidity. So instead of erroring out when $ROOTFS_DIR/dev doesn't exist, we create it. Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
* initramfs-framework: modify the fatal behaviour in initChen Qi2014-06-161-4/+1
| | | | | | | When a fatal error occurs, we'd better drop into a shell instead of having it sleep for 3600 seconds. Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
* initramfs-framework: fix an error in udev moduleChen Qi2014-06-161-0/+1
| | | | | | | The /var/run directory needs to be there in order for udevd to work correctly. Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
* initramfs-image-minimal.bb: add recipeChen Qi2014-06-161-0/+19
| | | | | | | | | | | | | | | | Add a recipe for a minimal initramfs image. Note that the purpose of this recipe is totally different from that of core-image-minimal-initramfs.bb. The latter is supposed to be used in the live image to "boot" or "install". The former is more like a traditional initramfs whose responsibility is to deal with the kernel parameters and then bring up the real root file system. After adding this recipe, we could specify INITRAMFS_IMAGE to be "initramfs-image-minimal". Note that in OE, we didn't have a reference image recipe for INITRAMFS_IMAGE. Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
* alsa-tools: Add missing pkgconfg dependencyRichard Purdie2014-06-141-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* neard: fix more parallel build issuesRoss Burton2014-06-143-32/+41
| | | | | | | | | | One fix, another appears... root-cause to a magic dependency hiding at the bottom of the Makefile, and add all binaries to it. [ YOCTO #6416 ] Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* native.bbclass: Properly define directoriesMatthieu Crapet2014-06-142-2/+8
| | | | | | | | | | | | | | | | For most users this commit will have no effect. But if you come across the idea of giving different names for paths, you'll get some troubles. When a recipe inherit native, properly define bindir, sbindir, includedir, sysconfdir, datadir (using xxxdir_native definitions from meta/conf/bitbake.conf). For example, edit "${BASE_WORKDIR}/${MULTIMACH_TARGET_SYS}/quilt-native/temp/log.do_configure" and see what are the arguments given by oe_runconf. Notice that ${docdir}, ${mandir}, ${infodir}, ${localstatedir} have no associated _native definition. Signed-off-by: Matthieu Crapet <Matthieu.Crapet@ingenico.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf/qemu: Move QEMU_OPTIONS to qemu.bbclassRichard Purdie2014-06-142-13/+12
| | | | | | | | The QEMU_OPTIONS variables belong in qemu.bbclass so move them there. The only users of them inherit qemu.bbclass. There is no point in pushing these into every recipe. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuwrapper-cross: Use QEMU_OPTIONSRichard Purdie2014-06-141-1/+2
| | | | | | | | The correct cpu options are needed in order to correctly run some CPU types. This information is available in QEMU_OPTIONS, use it. This avoids architectures like qemuppc failing postinstalls. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Add QEMU_OPTION for ppc7400 as used by qemuppcRichard Purdie2014-06-141-0/+1
| | | | | | | | | Currently, qemuppc prints warnings about gdk-pixbuf postinstalls not working due to illegal instructions. This is due to qemu running with the wrong cpu type. Add an option for ppc7400 so that qemuppc works correctly. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* git: don't hardcode the full path to perlChristopher Larson2014-06-141-0/+1
| | | | | | | | | Hardcoded paths to perl don't make sense, use from the environment instead. [Patch taken from meta-mentor by RP] Signed-off-by: Christopher Larson <kergoth@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildstats-summary.bbclass: Import useful bbclass from meta-mentorMartin Jansa2014-06-141-0/+39
| | | | | | | | | This class summarizes sstate reuse at the end of the build, so you know how much of your build was done from scratch. Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Christopher Larson <kergoth@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* git: revert to wrapper based relocationChristopher Larson2014-06-141-2/+14
| | | | | | | | | | | | | | | | | | It seems that there are multiple problems with the upstream RUNTIME_PREFIX mechanism at this time. It doesn't canonicalize argv[0] to an absolute path, breaking calls via the PATH, for example. In addition, it doesn't seem to locate template_dir via the runtime prefix even when specified as relative. Revert this for now to the previous wrapper-based mechanism, but tweaked slightly to avoid hardcoding the sysroot path into the wrapper (based on the bits in the rpm recipe). [YOCTO #6211] [Pulled from meta-mentor by RP] Signed-off-by: Christopher Larson <kergoth@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* busybox: handle syslog related files properlyChen Qi2014-06-141-11/+14
| | | | | | | | | | | | | | | | | | | If CONFIG_SYSLOGD is not enabled, then the related service file should not be installed as it will always fail at system start-up. The error message is as following. [FAILED] Failed to start System Logging Service. The same logic applies to CONFIG_KLOGD. So we should first check the configuration before we install these service files. [YOCTO #5302] Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* curl: control ipv6 support based on DISTRO featureAndre McCurdy2014-06-141-0/+6
| | | | | | | | | | | | | By default ipv6 is auto detected for native builds but disabled when cross compiling. This commit adds a PACKAGECONFIG option, unconditionally enabled for native and nativesdk builds and controlled by the ipv6 DISTRO feature for target builds. Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gstreamer1.0-rtsp-server: depends on libcgroup and gstreamer1.0-plugins-baseRobert Yang2014-06-141-1/+1
| | | | | | | | | | | | | Otherwise may do_compile error: test-cgroups.c:43:23:: fatal error: libcgroup.h: No such file or directory and: configure: No package 'gstreamer-plugins-base-1.0' found Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* stat: use update-alt for statSaul Wold2014-06-141-2/+9
| | | | | | | | | | | Three different recipes provide the stat program, busybox, coreutils and stat. Ensure that they are installed to the same place and use update-alternative with the correct priorities to have the correct binary installed. [YOCTO #6415] Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* e2fsprogs: use update-alt for chattrSaul Wold2014-06-141-0/+9
| | | | | | | | | | | Both busybox and e2fsprogs provide chattr, ensure that they are delivered to the same location and use update-alternatives to ensure the correct links are there. [YOCTO #6407] Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* texinfo-dummy-native: Fix dummy scripts failing when paths contain capital EsMax Eliaser2014-06-141-1/+1
| | | | | | | | This was an issue in the command-line argument parsing. It was the cause of the bug reported on the OE-core mailing list by Denys Dmytriyenko. Signed-off-by: Max Eliaser <max.eliaser@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* default-distrovars.inc: Remove unused variable 'LIMIT_BUILT_LOCALES'Jacob Kroon2014-06-132-4/+1
| | | | | | | | | | | This variable is a left-over from early glibc recipes. It is not referenced anymore in oe-core, and its functionality has been replaced with 'GLIBC_GENERATE_LOCALES'. Also remove the reference to it in local.conf.sample.extended. Signed-off-by: Jacob Kroon <jacob.kroon@mikrodidakt.se> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dbus: fixed mode if systemd service fileEnrico Scholz2014-06-131-1/+1
| | | | | | | | | | | | systemd complains with | Configuration file /lib/systemd/system/dbus.socket is marked executable. Please remove executable permission bits. Proceeding anyway. | Configuration file /lib/systemd/system/dbus.service is marked executable. Please remove executable permission bits. Proceeding anyway. else. Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dbus: disable usage of dbus-glib explicitlyEnrico Scholz2014-06-131-1/+2
| | | | | | | | | | | | | | | | | | on rebuilds, dbus-native can detect an already existing dbus-glib and tries to link some tests against it. As files were unstaged and due to libtool insanities this fails with: | /usr/bin/grep: .../sysroots/x86_64-oe-linux/usr/lib/libdbus-1.la: No such file or directory | sed: can't read .../sysroots/x86_64-oe-linux/usr/lib/libdbus-1.la: No such file or directory | x86_64-oe-linux-libtool: link: `.../sysroots/x86_64-oe-linux/usr/lib/libdbus-1.la' is not a valid libtool archive | make[3]: *** [libdbus-testutils.la] Error 1 | make[3]: Leaving directory `.../work/x86_64-oe-linux/dbus-native/1.8.2-r0/build/test' Make builds predicatable (and working) by disabling usage of dbus-glib explicitly. Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bluez5: Force obex.service in /usr/libDrew Moseley2014-06-131-1/+1
| | | | | | | | | Upstream bluez installs the obex.service file into /usr/lib regardless of the multilib settings as does the current systemd recipe. Make sure it gets packaged properly. Signed-off-by: Drew Moseley <drew_moseley@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* elfutils: Fix debugedit failure in grubRichard Purdie2014-06-132-7/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | We've seeing occasional debugedit failures in grub during do_package which in turn are coming from section alignment failures from libelf. The failures occur when gold is used to link grub instead of ld.bfd. "readelf -e uhci.module" shows: Section Headers: [Nr] Name Type Addr Off Size ES Flg Lk Inf Al [12] .note.GNU-stack PROGBITS 00000000 0010ce 000000 00 0 0 1 in a good build and: Section Headers: [Nr] Name Type Addr Off Size ES Flg Lk Inf Al [24] .note.GNU-stack PROGBITS 00000000 009180 000000 00 0 0 0 in a bad build. The problem is the "Al" (alignment) change from 1 to 0. If its 0, debugedit complains. As far as I can tell, the alignment of a zero length section is not an issue and the check in libelf should check the section size and only give alignment errors if there is some data to align. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* git: fixed typo in 'libexecdir' varnameEnrico Scholz2014-06-131-1/+1
| | | | | | | variable is called 'libexecdir', not 'libxecdir'. Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/test-remote-image: Add script for running runtime tests on remotely ↵Corneliu Stoicescu2014-06-131-0/+340
| | | | | | | | | | | | | | built images YB: #6254 Adding a new script that will fetch image files from a remote images repository. These images will then be used for local runtime testing. Use the '-h' option for more details on usage. Signed-off-by: Corneliu Stoicescu <corneliux.stoicescu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* controllers/masterimage.py: Make testimage kernel naming pattern universalCorneliu Stoicescu2014-06-131-1/+1
| | | | | | | | | | | | YB: #6254 The QemuTargetControl class does not specify any kernel naming but the runqemu script it uses uses the " KERNEL_IMAGETYPE + MACHINE + '.bin' " naming scheme. Modifying the other major target controller class, MasterImageHardwareTarget, to use the same kernel naming scheme. This is usefull also to outside scripts that want to anticipate the kernel file name for all target controllers. Signed-off-by: Corneliu Stoicescu <corneliux.stoicescu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/controllers/testtargetloader.py: add 'import os'Corneliu Stoicescu2014-06-131-0/+1
| | | | | | | | | YB: #6254 This module uses os but relies on other modules to import it. Adding 'import os' in order to be self-sustained. Signed-off-by: Corneliu Stoicescu <corneliux.stoicescu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* targetcontrol.py: Add a classmethod to get extra files needed by the target ↵Corneliu Stoicescu2014-06-131-0/+4
| | | | | | | | | | | | controllers YB: #6254 Add a new classmethod that can be used by outside scripts to get the extra files needed by the target controllers. An outside script can predict rootfs, manifest and kernel files needed by a target controller, but sometimes there are other files needed. Signed-off-by: Corneliu Stoicescu <corneliux.stoicescu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-testmaster.bb: add bzip2 to imageCorneliu Stoicescu2014-06-131-1/+1
| | | | | | | | | YB: #6375 Some test image fstypes require bzip2 decompression. Signed-off-by: Corneliu Stoicescu <corneliux.stoicescu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* masterimage.py: enable dynamical determination of rootfs typeCorneliu Stoicescu2014-06-131-3/+6
| | | | | | | | | YB: #6375 Adding support for get_image_fstype() in the MasterImageHardwareTarget and GummibootTarget classes. Signed-off-by: Corneliu Stoicescu <corneliux.stoicescu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* targetcontrol.py: make possible dynamical determination of rootfs typeCorneliu Stoicescu2014-06-131-2/+17
| | | | | | | | | | | | YB: #6375 Added a new method get_image_fstype() that autodetermines what fstype to use for the rootfs file. This method uses a new list variable 'supported_image_fstypes' that contains image fstypes supported by the target controller. This method is also a classmethod which means outside scripts can get the image fstype. Signed-off-by: Corneliu Stoicescu <corneliux.stoicescu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kexec-tools: Refine kdump device_tree sortChong Lu2014-06-132-1/+84
| | | | | | | | | | | | | The commit b02d735bf was to rearrange the device-tree entries, and assumed that these entries are sorted in the ascending order. but acctually when I was validating kexec and kdump, the order of serial node still is changed. So the patch is to sort these entries by the directory name in ascending order. Signed-off-by: Yang Wei <Wei.Yang@windriver.com> Signed-off-by: Chong Lu <Chong.Lu@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oprofile: Determine the root home directory dynamicallyChong Lu2014-06-133-116/+122
| | | | | | | | | | | | | | | This commit detects the root home directory dynamically with changes to the opcontrol script and the oprofile gui app source. The commit replaces an earlier fix that detected and adjusted a 'non-standard' root home directory at build time. The advantage of this patch is that the oprofile tools are adjusted to the current run-time path to ~root, not the build time path. Signed-off-by: Dave Lerner <dave.lerner@windriver.com> Signed-off-by: Chong Lu <Chong.Lu@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perf: split packgingHenning Heinold2014-06-131-5/+17
| | | | | | | | | | | | | | * some fundamental perf commands can work without the dependency on perl, python or bash make them separate packages and RSUGGEST them * bump PR The patch was sponsored by sysmocom Signed-off-by: Henning Heinold <henning@itconsulting-heinold.de> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perf: fix broken shell comparsion in do_installHenning Heinold2014-06-131-1/+1
| | | | | | | | The patch was sponsored by sysmocom Signed-off-by: Henning Heinold <henning@itconsulting-heinold.de> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nfs-utils: Do not pass CFLAGS to gcc while buildingChong Lu2014-06-133-32/+43
| | | | | | | | | Do not pass CFLAGS/LDFLAGS to gcc while building, The needed flags has been passed by xxx_CFLAGS=$(CFLAGS_FOR_BUILD). Signed-off-by: Chong Lu <Chong.Lu@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sed: enable ptest supportChong Lu2014-06-133-3/+87
| | | | | | | | Install sed test suite and run it as ptest. Signed-off-by: Chong Lu <Chong.Lu@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* v4 cups: Shouldn't link against libgcrypt without using gcrypt functionsArmin Kuster2014-06-132-0/+50
| | | | | | | | | | Backported from http://www.cups.org/strfiles.php/3308/cups-no-gcrypt.patch This addresses the cryto dependency seen during build. Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* texinfo.bbclass: native/cross uses dummy texinfo; target uses host's Texinfo.Max Eliaser2014-06-132-1/+15
| | | | | | | | | | | | | To unpack that to more than a single line: -native and -cross recipes are made to use the dummy Texinfo utilities provided by texinfo-dummy-native if they invoke those utilities at build time. The target-architecture (cross-compiled) recipes still use the genuine Texinfo utilites. Right now, they still use the host system's Texinfo utilities, but could be made to use the texinfo-native recipe we already ship with some config file changes. Signed-off-by: Max Eliaser <max.eliaser@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* texinfo-dummy-native: Create recipe w/ scripts to stand in for Texinfo utils.Max Eliaser2014-06-133-0/+171
| | | | | | | | | | | | | | | | | | | | More work toward eliminating the dependency on the host system's Texinfo-- Python scripts that understand the same command-line options as the Texinfo utilities, and create blank output files if appropriate, but don't actually do any of the work done by those utilities. This will be necessary to avoid circular dependencies when we start explicitly tracking dependencies on texinfo-native; i.e. texinfo-native -> autoconf-native -> texinfo-native. If we have all native recipes that inherit texinfo.bbclass depend on texinfo-dummy-native instead of texinfo-native, the cycle is broken. It may also provide a performance gain by skipping the actual work of formatting and generating documentation files. Signed-off-by: Max Eliaser <max.eliaser@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* texinfo: Use texinfo-replacement-native as an alias for texinfo-native.Max Eliaser2014-06-131-1/+3
| | | | | | | | | | | | If texinfo-native is added to ASSUME_PROVIDED, this will be needed for two reasons. First, a world build will still build the native texinfo recipe, so it will still get test coverage and will not rot. Second, when the target architecture texinfo recipe is built, the native recipe must be built first so its makedoc binary can be extracted, ASSUME_PROVIDED or no. Signed-off-by: Max Eliaser <max.eliaser@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rootfs.py: change the logic in _uninstall_unneededChen Qi2014-06-131-5/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | Previously, if we have 'package-management' and 'read-only-rootfs' both in IMAGE_FEATRUES, we would meet the following error at system start-up. rm: can't remove '/etc/rcS.d/S99run-postinsts': Read-only file system However, what's really expected is that when there's no postinstall script at system start-up, the /etc/rcS.d/S99run-postinsts should not even be there. Whether or not to remove the init script symlinks to run-postinsts should not depend on whether we have 'package-management' in IMAGE_FEATURES; rather, it should only depend on whether we have any postinstall script left to run at system start-up. This patch changes the _uninstall_unneeded function based on the logic stated above. [YOCTO #6257] Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm: Fix cpio 32 bit overflow issues on 64 bit inode filesystemsRichard Purdie2014-06-123-0/+189
| | | | | | | | | | When building on XFS filesystems, the resulting rpms can be corrupted with the same inode number being used for multiple hardlinked files. There are two fixes, one to stop rpm crashing when accessing a broken binary rpm, the other to stop generating them in the first places. Full descriptions in the patch headers. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "fontconfig: enable 64 bit file support"Ross Burton2014-06-101-2/+0
| | | | | | | | | | Fontconfig doesn't need to be passed large file flags through CPPFLAGS because it's configure script uses AC_SYS_LARGEFILE. This reverts commit 5a49a24d35794fcf9e3895469a67db992a52305e. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>