summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* libpam: add PACKAGECONFIG data concerning auditJoe Slater2013-08-261-0/+2
| | | | | | | | | | | | | We do not want libpam to build using audit just because it happens to be lying around, so we create PACKAGECONFIG[] data to give us explicit control. (From OE-Core rev: 4db6aa2094447f8d2a9c234089a80ddcd78fcbd0) Signed-off-by: Joe Slater <jslater@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cronie: add PACKAGECONFIG dataJoe Slater2013-08-261-6/+7
| | | | | | | | | | | We add PACKAGECONFIG[] data for audit and move the current pam related stuff into it's own entry. (From OE-Core rev: ada22cab96bb6b7cc98782a14e7c44fbebde77df) Signed-off-by: Joe Slater <jslater@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* e2fsprogs: add populate-extfs.shRobert Yang2013-08-262-0/+97
| | | | | | | | | | | | | | | | | | | | | | | | | | | This script is originally from Darren Hart, it will be used for creating the ext* filesystem from a given directory, which will replace the genext2fs in image_types.bbclass at the moment, we may use the mke2fs to replace this script again when it has the initial directory support. Changes of the script: * Rename it from mkdebugfs.sh to populate-extfs.sh * Add a simple usage * Add checking for the number of the parameters * Add the "regular empty file" and "fifo" file type * Set mode, uid and gid for the file * Save the command lines to a file and batch run them * Change the error message * Improve the performance * Add the support for hardlink [YOCTO #3848] (From OE-Core rev: 265f91149aa8c475ebe5b7069044ed94b7857fa9) Signed-off-by: Darren Hart <dvhart@linux.intel.com> 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>
* e2fsprogs: properly set up extent header in do_writeRobert Yang2013-08-262-0/+49
| | | | | | | | | | | | | | | | | | | | | | do_write doesn't fully set up the first extent header on a new inode, so if we write a 0-length file, and don't write any data to the new file, we end up creating something that looks corrupt to kernelspace: EXT4-fs error (device loop0): ext4_ext_check_inode:464: inode #12: comm ls: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0) Do something similar to ext4_ext_tree_init() here, and fill out the first extent header upon creation to avoid this. [YOCTO #3848] (From OE-Core rev: 7d1e51681d25f6e6d2c20744825723ad5c83861c) 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>
* e2fsprogs: only update the icache for ext2_inodeRobert Yang2013-08-262-0/+70
| | | | | | | | | | | | | | | | | | | | | | | | | | We only read the cache when: bufsize == sizeof(struct ext2_inode) then we should only update the cache in the same condition, otherwise there would be errors, for example: cache[0]: cached ino 14 when bufsize = 128 by ext2fs_write_inode_full() cache[1]: cached ino 14 when bufsize = 156 by ext2fs_read_inode_full() Then update the cache: cache[0]: cached ino 15 when bufsize = 156 by ext2fs_read_inode_full() Then the ino 14 would hit the cache[1] when bufsize = 128 (but it was cached by bufsize = 156), so there would be errors. [YOCTO #3848] (From OE-Core rev: ad8452196c5b1a54c14fd00bbf421f68aea65186) 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>
* e2fsprogs: let debugfs do sparse copyRobert Yang2013-08-262-0/+149
| | | | | | | | | | | | | | | | Let debugfs do sparse copy when src is a sparse file, just like "cp --sparse=auto" This patch has been reviewed by the linux-ext4 mailing list, but isn't merged atm. [YOCTO #3848] (From OE-Core rev: 723adaf8fbba61b7f1adc8e4a13ddf1cfb5c0bcf) 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>
* e2fsprogs: the max length of debugfs argument is too shortRobert Yang2013-08-262-0/+42
| | | | | | | | | | | | | | | | | | The max length of debugfs argument is 256 which is too short, the arguments are two paths, the PATH_MAX is 4096 according to /usr/include/linux/limits.h, so use BUFSIZ (which is 8192 on Linux systems), that's also what the ss library uses. This patch has been reviewed by the linux-ext4 mailing list, but isn't merged atm. [YOCTO #3848] (From OE-Core rev: a916a127768291ca7c614976e05c90153fec2956) 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>
* oe.types: add 'path' typeChristopher Larson2013-08-261-0/+18
| | | | | | | | | | | | - path normalization ('normalize' flag, defaults to enabled) - existence verification for paths we know should exist ('mustexist' flag) - supports clean handling of relative paths ('relativeto' flag) (From OE-Core rev: a598242197312fa6d43179c283da2d0873de2919) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* stat: fix the wrong return codeZhangle Yang2013-08-262-1/+18
| | | | | | | | | | | After stat -h is executed, the return code is 1. This patch changes it to 0. (From OE-Core rev: c10435025f5c51c4827d71af82a9a517f5f8f6d8) Signed-off-by: Zhangle Yang <zhangle.yang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gtk-engines: fix build with automake-1.13Marko Lindqvist2013-08-262-1/+39
| | | | | | | | | | | | Add patch substitute-tests.patch that works around automake TESTS limitation. See http://debbugs.gnu.org/cgi/bugreport.cgi?bug=13771. (From OE-Core rev: ace40e1dfcaca2aa1eae2daf29c812291063fbff) Signed-off-by: Marko Lindqvist <cazfi74@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pulseaudio: Fix up configure options and use gtk+3Saul Wold2013-08-261-9/+2
| | | | | | | (From OE-Core rev: b51bfbc304eba448b9913d36444d70a643564c64) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* alsa-lib: fix function definitions error for mipsKai Kang2013-08-262-0/+69
| | | | | | | | | | | | | | | | | | | | Functions atomic_add(s) and atomic_sub(s) are defined with 'extern __inline__' that may cause compile fails when cross compile for mips. The error message looks like: | pcm/.libs/libpcm.a(pcm_meter.o): In function `snd_pcm_meter_update_scope': | .../alsa-lib-1.0.27.2/src/pcm/pcm_meter.c:139: undefined reference to `atomic_sub' Replace the 'extern __inline__' with 'static __inline__' to fix this issue. (From OE-Core rev: 80b4eb9e12ccf815261f6a67fd9b8d97717e82d5) Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* connman: upgrade to 1.17Cristian Iorga2013-08-261-2/+2
| | | | | | | | | | | connman 1.17 is mainly a bugfix release, as such, recommended to upgrade to. (From OE-Core rev: ad98f2bfa2c6ebb53b9c1fa4afad8842ab65062c) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* harfbuzz: upgrade to v0.9.19Mihai Prica2013-08-262-20/+13
| | | | | | | | | | | | | | | Remove the disable_graphite.patch because the --without-graphite2 configure option can be used instead. Split package into harfbuzz and harfbuzz-icu. The ICU support is now built into a separate library that will be shipped in a different package. (From OE-Core rev: c93d147e0889ac91a01e3570f818624f68b3c8e8) Signed-off-by: Mihai Prica <mihai.prica@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gpgme: update to 1.4.3Paul Eggleton2013-08-262-2/+3
| | | | | | | | (From OE-Core rev: 3b4f5c4153c0af0e5205d9c30e4b7265c36079d3) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu-ifup: when tunctl can't be found, say what package builds itRoss Burton2013-08-261-1/+1
| | | | | | | | | | | | | If runqemu is used without actually building any qemu images (i.e. you downloaded the images) it's likely that qemu-helper-native hasn't been built. Instead of just saying what command can't be found, tell the user how to solve their problem. (From OE-Core rev: 45f80a0c46035dc73818ce4bd818a4f6197d954f) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openssl: avoid NULL pointer dereference in three placesXufeng Zhang2013-08-263-0/+62
| | | | | | | | | | | | | | | | There are three potential NULL pointer dereference in EVP_DigestInit_ex(), dh_pub_encode() and dsa_pub_encode() functions. Fix them by adding proper null pointer check. [YOCTO #4600] [ CQID: WIND00373257 ] (From OE-Core rev: 4779d3c89cf0129763a4f5b7306c1247a0d6d021) Signed-off-by: Xufeng Zhang <xufeng.zhang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openssh: add init.d/sshd status command for LSB complianceJackie Huang2013-08-261-1/+9
| | | | | | | | | (From OE-Core rev: d1e518b6942b945be7a4d44bc137a1441af8f837) Signed-off-by: Li Wang <li.wang@windriver.com> Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* at: add init.d/atd status command for LSB complianceJackie Huang2013-08-261-1/+7
| | | | | | | | | (From OE-Core rev: 9c19592afac6b38df7038da02bcda26dc28b4e4c) Signed-off-by: Li Wang <li.wang@windriver.com> Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sysvinit: add init.d/bootlogd status command for LSB complianceJackie Huang2013-08-261-1/+8
| | | | | | | | | (From OE-Core rev: 95180b966adb6ebe6451ab0e91187e7db93f22e4) Signed-off-by: Li Wang <li.wang@windriver.com> Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dbus: add init.d/dbus-1 status command for LSB complianceJackie Huang2013-08-261-1/+8
| | | | | | | | | (From OE-Core rev: 9262d3b06eee7e698c990399d2f10b7d68d17211) Signed-off-by: Li Wang <li.wang@windriver.com> Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nfs-utils: add init.d/nfsserver status command for LSB complianceJackie Huang2013-08-261-0/+11
| | | | | | | | | (From OE-Core rev: d5132337fa08ee74eaebadaeaecb6b4f5b2c5190) Signed-off-by: Li Wang <li.wang@windriver.com> Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sysklogd: add init.d/syslog status command for LSB complianceJackie Huang2013-08-261-1/+12
| | | | | | | | | (From OE-Core rev: 7f0314c095032c231e2408c0276fea56b4e68884) Signed-off-by: Li Wang <li.wang@windriver.com> Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glib-2.0: Specify libiconv when building on uclibcKhem Raj2013-08-261-0/+1
| | | | | | | | | | | | | | | | | We use GNU libiconv seprate package on uclibc specifying this makes the configure clear of not trying to detect glibc/iconv and then also finding libiconv in sysroot and confusing itself with errors like | gconvert.c:66:2: error: #error GNU libiconv not in use but included iconv.h is from libiconv | #error GNU libiconv not in use but included iconv.h is from libiconv | ^ (From OE-Core rev: 38b6c4df7c215ed7fd6be107fbc2527e66791e2e) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: add 3.10 bbappend and update routerstationpro's preferred versionBruce Ashfield2013-08-262-1/+21
| | | | | | | | | | | | | | Now that the 3.10 yocto kernel tree is available, meta-yocto-bsp needs a bbappend with the relevant SRCREVs defined. Note: that only the routerstationpro is updated to 3.10, and the other reference BSPs continue to use their existing preferred versions. (From meta-yocto rev: 8e3688ea98ad06a64218a67d5ee4c96165766686) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: data_smart: Add _remove operatorRichard Purdie2013-08-261-5/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | There are long standing complaints about the fact its very difficult to remove a portion of a variable. The immediate request is for a -= and =- operator. The trouble is that += and =+ are "immediate" operators and are applied straight away. Most people would expect -= and =- to be deferred to have the effect most people desire and therefore implementing -= and =- would just make the situation more confusing. This deferred operation is much more similar to the override syntax which happens at data store finalisation. The _remove operator is therefore in keeping with the _append and _prepend operations. This code is loosely based on a patch from Peter Seebach although it has been rewritten to be simpler, more efficient and avoid some potential bugs. The code currently only works on space delimited variables, which are by far the most commom type. If bitbake is ehanced to support types natively in future, we can adjust this code to adapt to that. (Bitbake rev: 9c91948e10df278dad4832487fa56888cd58d187) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake: Add ui event handlers filteringRichard Purdie2013-08-265-8/+46
| | | | | | | | | | | | | | | | | | | Add functionality to allow UIs to update and change the types of events they recieve. To do this we need to add a new command and also need to be able to obtain the current event hander ID. In the case of xmlrpc, this is straightforward, in the case of the process server we need to save the result in a multiprocessing.Value() so we can retrive it. An excplit command was added to the server API to facilitate this. The same function can also be used to mask or unmask specific log messages, allowing the UI to optionally differ from the standard set of message filtering. Based upon work by Cristiana Voicu <cristiana.voicu@intel.com> (Bitbake rev: ba5a6c88785d9889d4172ec79937ac2a5555327e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: server/xmlrpc/prserv: Add sane timeout to default xmlrpc serverRichard Purdie2013-08-262-7/+18
| | | | | | | | | | | | | | | | | The standard python socket connect has long timouts which make sense for remote connections but not local things like the PR Service. This adds a timeout parameter to the common xmlrpc server creation function and sets it to a more reasonable 5 seconds. Making the PR server instantly exit is a good way to test the effect of this on bitbake. We can remove the bodged timeout in the PRServer terminate function which has the side effect of affecting global scope. (Bitbake rev: 8c01cff94787abbb64fbdf0c16cd63f8f97a7e03) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: process: Improve exit handling and hangsRichard Purdie2013-08-261-19/+17
| | | | | | | | | | | | | | | | | | | | | | | It turns out we have a number of different ways the process server termination can hang. If we call cancel_join_thread() on the event queue, it means that it can be left containing partial data. This means the reading of the event queue in the terminate() function can hang, the timeout and block parameters to Queue.get() don't make any difference. Equally, if we don't call cancel_join_thread(), the join_thread in terminate() will hang giving a different deadlock. The best solution I could find is to loop over the process is_alive() after requesting it stops, trying to join the thread and if that fails, try and flush the event queue again. It wasn't clear what difference a force option should make in this case, we're gracefully trying to empty queues and shut down regardless of whether its a SIGTERM so I've simply removed the force option. (Bitbake rev: c5c8f33ca4b81877a0115887849881001b745bf0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: parse: Return IOError when including file with absolute pathMartin Jansa2013-08-262-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * resolve_file was behaving different when relative and absolute paths were passed to it * include relative-path/non-existent-file.inc works correctly resolve_file throws IOError, BBHandler.py:handle() doesn't catch it, ConfHandler.py:include() catches IOError and shows: DEBUG: CONF file 'relative-path/non-existent-file.inc' not found * include /absolute-path/non-existent-file.inc was failing, because resolve_file just returns fn, BBHandler.py:handle() calls bb.parse.mark_dependency(d, abs_fn) which throws: OSError: [Errno 2] No such file or directory: '/absolute-path/non-existent-file.inc' and parsing fails. Ad isfile() test for absolute fn and throw IOError to make resolve_file behavior consistent for both paths. * I know we had some issues with -b relative-path-to-recipe.bb and absolute path, so consider this patch only as RFC and documentation of this problem * Catch OSError too in ConfHandler.py:include() e.g. in case the file exists, but user cannot read it or something like that. (Bitbake rev: b0bbd89a4f0b98fa1ab28b8e0526cd9ddb76fa57) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk-ca-certificates: prepopulate ca-certificates.crtChristopher Larson2013-08-261-0/+6
| | | | | | | | | | | As postinsts aren't run for nativesdk packages when populating an SDK, we need to prepopulate up-front. (From OE-Core rev: 09e768b68b3605e897d422c9c7b3815f3b994d31) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ca-certificates: add recipe (version 20130610)Christopher Larson2013-08-265-0/+239
| | | | | | | | | | | | | | | | | | | | | | | | | We need this for certain nativesdk recipes, as we can't rely on the certificate path or bundle path being the same across distros, and it's useful in many cases on the target as well. This is based on the 20130119 recipe from meta-oe, with the following changes: - use the debian git repository to avoid vanishing sources - obey our target paths - default to a sysroot relative to the script location (make relocatable) - define SUMMARY - don't inherit autotools, this isn't an autotools package - add MPL-2.0 to LICENSE, as that's the license of the certdata - install the script man page - use a native rather than cross recipe, as it's not bound in any way to the target system - add nativesdk to bbclassextend, for use in SDKs (From OE-Core rev: ad2851cf0abc2ab35e0f60c96d3142c29a07c8fc) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xserver-nodm-init: improvements from meta-oePaul Eggleton2013-08-263-8/+41
| | | | | | | | | | | | | | | | | | | | | | Bring in some changes from the meta-oe version of this script in order to bring them closer together. (Unfortunately it does not completely supersede the recipes in meta-oe - there is still some unification to be done between x11-common and xserver-common.) * Add systemd support (with extensions for ROOTLESS_X) * Remove sudo from RDEPENDS_${PN} since this hasn't been used by this for a long time * Rearrange recipe slightly to make the order logical A couple of additional improvements at the same time: * Use ROOT_HOME for root's home directory * Set short description in SUMMARY instead of DESCRIPTION (From OE-Core rev: d4f82500fb30e9e25b517e65c2bd72b3c2bad070) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes: Remove references to _remove in function names since this may ↵Richard Purdie2013-08-266-15/+15
| | | | | | | | | | | | | | become a bitbake keyword There is a good chance we might want to support a bitbake operator "_remove" which works in a similar way to _append and _prepend. As such, we can't use those keywords in function or variable names. (From OE-Core rev: 491fde8cd3fd493f9fec2fd434fe1be547f66148) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: introduce v3.10Bruce Ashfield2013-08-263-0/+85
| | | | | | | | | | | | | | | | | | | | | | | | | | | Introduce the 3.10 kernel. This is based on the 3.10.9 upstream kernel and replaces the 3.8 recipes, which will be removed once all reference boards have been updated. 3.10 also the latest LTSI and will be updated with that content when it becomes available. Other features of the 3.10 kernel include: - refreshed -rt support - refreshed yaffs2, aufs3 - cryptodev - bfs, edf, and OCF staged features - scrubbed and updated meta data for v3.10 - improved tools support for meta data updates and queue maintenance - patch carry forward from all previous linux-yocto kernels and configuration. This kernel has been built and boot tested on all qemu machines and architectures. (From OE-Core rev: 6dc46834c6edaf358c18b26e4304bc9e7413eb60) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gst-plugins-good: fix 3.10 libc-headers build failureBruce Ashfield2013-08-262-0/+46
| | | | | | | | | | | | | | | | kernel commit 24b9f5017 [[media] V4L: Remove deprecated image centering controls] removed the definitions of V4L2_CID_HCENTER and V4L2_CID_VCENTER after three years of depreciation. The ioctl values are still free, and the case statement which processess them in v4l2 userspace falls through to the proper replacement. So in the short term, we can explicitly define them using the old absolute values, and everything will work. (From OE-Core rev: 1e35d04067357b1c65d9e2c4796acfa02274fd9d) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-libc-headers: Reinstate ↵Richard Purdie2013-08-262-12/+12
| | | | | | | | | | | | scripts-Makefile.headersinst-install-headers-from-sc.patch The autobuilders and their long paths are still triggering errors during the headers installation. Reinstate the previous patch for this, after updating for 3.10. (From OE-Core rev: fe4428fd740b3937007e0a3f893714ff04c33533) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-libc-headers: ptrace.h: remove ptrace_peeksiginfo_argsBruce Ashfield2013-08-262-1/+51
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The addition of ptrace_peeksiginfo_args to the uapi in kernel commit 84c751bd [ptrace: add ability to retrieve signals without removing from a queue (v4)] means that existing applications using glibc versions that define ptrace_peeksiginfo_args in sys/ptrace.h will get duplicate structure definitions like: | In file included from /poky-master/build/tmp/work/i586-poky-linux/strace/4.8-r0/strace-4.8/process.c:66:0: | /poky-master/build/tmp/sysroots/qemux86/usr/include/linux/ptrace.h:58:8: error: redefinition of 'struct ptrace_peeksiginfo_args' | struct ptrace_peeksiginfo_args { | ^ | In file included from /poky-master/build/tmp/work/i586-poky-linux/strace/4.8-r0/strace-4.8/defs.h:159:0, | from /poky-master/build/tmp/work/i586-poky-linux/strace/4.8-r0/strace-4.8/process.c:37: | /poky-master/build/tmp/sysroots/qemux86/usr/include/sys/ptrace.h:191:8: note: originally defined here | struct ptrace_peeksiginfo_args | ^ | make[2]: *** [process.o] Error 1 Reverting to the previous status of not exporting this structure temporarily fixes applications, until they can be adjusted to not mix sys/ptrace.h and linux/ptrace.h includes. (From OE-Core rev: 7c207e4c3c0e3b575c67a302b97b0dc700a8fc15) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-libc-headers: update to v3.10Bruce Ashfield2013-08-263-9/+8
| | | | | | | | | | | | Now that the 3.10 kernel has been released we can bump the libc-headers to that version and remove the 3.8 variant. Userspace compatibility is maintained through kernel versions, we also make the single 3.10 version the toolchain default. (From OE-Core rev: 4e79a46254e778f85c00efd4b0085cbaeb6e0d4d) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* guilt: update to latest git versionBruce Ashfield2013-08-2614-869/+26
| | | | | | | | | | | | | | | | | Uprev guilt to the latest guilt version from its upstream repository. As part of the uprev all of the previous changes required for the yocto kernel tools to use git to manipulate series files have been dropped. These changes were specific to circumventing parts of guilt's internal santiy checking to allow specific Yocto kernel manipluation of sub-series files. Since the kernel tools no longer need guilt, we can use an up to date and nearly pure upstream version of guilt. (From OE-Core rev: 595c4469adc36d88ba2403915fc6c1d355014a58) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kern-tools: usability, bug fixes and no guiltBruce Ashfield2013-08-262-3/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Updating the kern-tools SRCREV to pick up the following fixes: 60a894e kgit-s2q: add proper commit ID handling for mixed am/apply usage 3b08257 kgit-s2q: delete pruning of path support. c5868b4 kgit-s2q: Restore implicit exit status to "git apply" section 1bd00b9 kgit-scc: mask warnings from cleanup phase 5 bb75299 kgit-s2q: fix commit warp when running "git am --abort" ef9571b kgit-scc: cleanup git rebase-apply dir fdb7d21 kgit-scc: ensure treegen stops if a meta series fails 008987b config: add kconfig cleaning options 69ff569 kgit-s2q: strip blank lines and comments e7b4540 kgit-init: disable garbage collection on a new tree 417eaed kgit-s2q: delete old LTSI patch dir finding code 21f2200 kgit-scc: better error checking on resume ad5084c kern-tools: use .meta as meta data container 1deb5d8 kgit-meta: don't push patches without a series file eb431a1 kgit-s2q: aid patch reject resolution via helper scripts f859c40 kgit-s2q: only use patch annotations when explicitly asked 333ae18 kgit: speed patch application by batching patches bf6991d kgit: teach tools about non-default meta dirs bcfc712 kgit-s2q: usability improvements cb28803 kgit-s2q: fix patch prefix stripping. 37f40e1 kgit-s2q: warn/exit with error if patch not in series f4704d2 kgit-s2q: consistent rm usage e11819c kgit-s2q: standardize on use of git mailinfo 36a5eda kgit: remove guilt dependency c461a4f spp/scc: export mark commands to meta-series 5311162 updateme: ensure that generated features are only used once 4f7a263 kgit-checkpoint: clear .gitignore for meta branch 21ee6f2 updateme: enforce a matching machine b08749d kgit-scc: remove -meta files after consruction These are bug fixes, usability changes as well as the removal of the guilt dependency. During the uprev of the guilt package, the amount of circumvention of the typical guilt workflow and checks meant that using it as a series -> branch manager was no longer appropriate. As a result a new tools kgit-s2q (series 2 queue) was created based on git-quiltimport, git am, and the LTSI tree generation scripts. The result is better series to branch validation, faster application and a simpler management model. This tool is backwards compatible with any tree previously constructed with guilt. We are now "guilt free" (From OE-Core rev: 983bff587b60fdd0244ad00f238df5ed50cc1e1a) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add memory resident bitbake scriptRichard Purdie2013-08-261-0/+55
| | | | | | | | | | | | | | | | | | | | | | | | This adds an init script which instead of the standard bitbake, launches a memory resident bitbake, defaulting to port 12345. It expects a port number to use as the first option. Right now this is experimental but I think its probably worth wrapping up in a form people can more easily experiment with it. There are some known issues: a) It throws some debug output due to the lack of a UI which we need to clean up b) It should probably be able to auto select a free port c) You get a nice backtrace if you specify a build directory but not a port number I'd also highlight there are security issues here if you don't trust users who can connect into localhost. We might need to look at named pipes or something similar for something limited to the current user. (From OE-Core rev: 52c7f8bba86a43b89f24a23d545c99d75b67555f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual, mega-manual: Updated figure for conf/compile detailsScott Rifenbark2013-08-262-0/+0
| | | | | | | | | | | | Fixes [YOCTO #2808] Updated the figure per Paul Eggleton's feedback to be clearer. The figure resides in both the ref-manual and the mega-manual. (From yocto-docs rev: 8a0f391c9404582b3b7f62d740d5c0488a6220be) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-project-qs, adt-manual: Updates to toolchain installer scriptScott Rifenbark2013-08-262-26/+51
| | | | | | | | | | | The way in which the toolchain installer scripts are named has changed. I have updated two sections that describe this so that the new naming scheme is used. (From yocto-docs rev: 71b70a12c72bca7cad565b5d6f44b2c6b311844d) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky.ent: Reset the toolchain variable.Scott Rifenbark2013-08-261-1/+1
| | | | | | | | | | I had to undo this change. The variable that points to the toolchains still needs to be in place. (From yocto-docs rev: 56382d447ef838ec50bae476d026016dabb4663b) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky.ent: Changed the toolchain variableScott Rifenbark2013-08-261-1/+1
| | | | | | | | | | | | Updated the YOCTO_TOOLCHAIN_DL_URL variable to be set to "&YOCTO_RELEASE_DL_URL;/buildtools/". This variable used to be set to "&YOCTO_RELEASE_DL_URL;/toolchains/". The naming scheme has changed for where toolchain installers are now built. (From yocto-docs rev: 376cce752784da6fbb1bdbf655c7f40d9766e9e4) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Makefile: Added new figure for package creation.Scott Rifenbark2013-08-261-2/+4
| | | | | | | | | | | | | Fixes [YOCTO #2808] The new section on package creation required a new figure. I added the figure to the TARBALL creation part for both the ref-manual and the mega-manual. (From yocto-docs rev: 3e752dd95659282833519bff866adc940a156ba7) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual, mega-manual: New section on package creationScott Rifenbark2013-08-263-0/+54
| | | | | | | | | | | | | | Fixes [YOCTO #2808] Added a new section to the expanded discussion on how builds are done. This section is on package creation. A new figure was added to both the ref-manual and mega-manual figures directories. (From yocto-docs rev: e31e5aeb7d93f3cfa4fc9c12e324f03a27b5f8ed) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Makefile: Added figure to the ref-manual and mega-manualScott Rifenbark2013-08-261-2/+2
| | | | | | | | | | | | | | Fixes [YOCTO #2808] A new figure named configuration-compile-autoreconf.png was introduced in a new section. Thus, the figure had to be added to the tarball creation for both the ref-manual and the mega-manual. (From yocto-docs rev: aa0967ee49fa5d8053e14e0cc229b47a0e65b1f9) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ref-manual, mega-manual: new section on config/compile for expanded buildScott Rifenbark2013-08-263-0/+59
| | | | | | | | | | | | | | Fixes [YOCTO #2808] Added a new section on configuration and compilation for the expanded discussion for the build process. This involved a new figure that had to be added to both the ref-manual and mega-manual figures directories. (From yocto-docs rev: 9ba90c79990b79226d6e95e4a01ddedeccb94b35) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-16 16:04:14 +0000