summaryrefslogtreecommitdiffstats
path: root/scripts
Commit message (Collapse)AuthorAgeFilesLines
...
* mkefidisk: Remove startup.nshDarren Hart2013-03-221-4/+0
| | | | | | | | | | | | | | | Most firmware implementations use the EFI specified EFI/BOOT/bootia32.efi (and similar) boot paths. Only broken firmware uses different paths for removable media. In those cases, the user can add their own startup.nsh. For the compliant case, selecting "Shell" from the EFI boot menu should go to the shell. (From OE-Core rev: d031cdbf40231b8c103d78c69252bf9d584d0605) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mkefidisk: Always use rootwait and document kernel parameters usedDarren Hart2013-03-221-8/+8
| | | | | | | | | | | | | | | | Without a reliable way of knowing if the target device with be an asyncronous block device on the target (MMC or USB), err on the side of caution of always specifcy "rootwait", ensuring the kernel will wait for the device to appear and not abort if it hasn't appeared in time for mount. Document the remaining kernel parameters added by this script on the same line as rootwait. (From OE-Core rev: 5b6a6a3872fd341cf978be40c69707223e3c29df) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mkefidisk: Boot with ro kernel parameter instead of rwDarren Hart2013-03-221-1/+1
| | | | | | | | | | | | | | | | | There is no need to boot with "rw". Booting with "ro" will allow for fsck to be run during boot, and a proper /etc/fstab will still ensure the rootfs is "rw" by the time the user can interact with the system. Change the "rw" to "ro" in the kernel parameters specified in the generated grub.cfg file. Fixes [YOCTO 4036] mkefidisk.sh hardcodes 'rw' as root mount option (From OE-Core rev: 960f0cbf85a4124adbc74d8b2ceb09a7d39ecc04) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mkefidisk: Cleanup comment lengthDarren Hart2013-03-221-2/+2
| | | | | | | | | | Keep comments under 80 characters in length. (From OE-Core rev: 1fbab279edd0057193900646cf9f66323698e774) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mkefidisk: Always specify a root= kernel parameterDarren Hart2013-03-221-2/+4
| | | | | | | | | | | | | | | | | The current script only replaces an existing root= kernel parameter which can result images created without a root= paremeter, even though the script expects a target rootfs parameter. Rather than replacing the root= parameter, delete the root= parameter if it exists, then append an appropriate root= parameter. Fixes [YOCTO 4035] mkefidisk.sh forgets to add root= parameter (From OE-Core rev: e5dbec7e7d3bb29676280823b0337ad429c75120) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/qemu-testlib: Add more debugging information1.4_M5.rc1Richard Purdie2013-03-211-10/+21
| | | | | | | | | | | | | This extra information should allow better forensics if the sanity tests fail as they're currently doing occasionaly on the autobuilder for unknown reasons. The patch also tightens up certain checks to remove pointless noise and error output from the logs. (From OE-Core rev: f9970aa0a44aca8ffe6c7a6a3261887fb0db38d2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/runqemu-internal: Fix lock racesRichard Purdie2013-03-201-12/+7
| | | | | | | | | | | | | | | | There are two problems here. Firstly the grep command is unanchored so pid 345 will match against 12345 and so on. The second issue is that there are several context switched between attempting the lock and then writing the pid to it. Between the two issues, there were issues appearing on the autobuilder due to these conflicts. This patch replaces the mechanism with flock on fd 8 which should be a safer mechanism to use. (From OE-Core rev: 98471be6e58451016200cfd10e64e8ae6266c801) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* runqemu: Improve error handling/exit codesRichard Purdie2013-03-202-17/+19
| | | | | | | | | | | | | runqemu-internal is sourced so should be returning with an error code in case of errors. runqemu needs to deal with this. This patch fixes up the various error paths so we're consistent and get a sane exit status for runqemu which helps a lot in its use in the qemu runtime testing on the autobuilder. (From OE-Core rev: 753533b2f338ff2ef97eebd5eace7623404ae457) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuimage-testlib: Add extra debugging and sanity checkRichard Purdie2013-03-201-1/+3
| | | | | | | | | | | Check for a zero IP address since its clearly incorrect if that value is found. Also add debugging for cases where we can't find the qemu process. A process listing is handy to help understand what the problem might be. (From OE-Core rev: 817a8dc6424050973d8fad4f003475ac83ea6bb5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuimage-testlib: Add delay to work around races in qemu startupRichard Purdie2013-03-201-0/+2
| | | | | | | | | | | Qemu changes pid when starting up. On a loaded machine, this can result in the incorrect pid being returned. Since qemu will take a few seconds to boot anyway, we might as well delay a short while and allow things to settle which should fix various race issues being seen on the autobuilder. (From OE-Core rev: c0cecc16d4305b16ecfb4a51f6d5020d34909794) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuimage-testlib: Fix IP address handlingRichard Purdie2013-03-191-4/+2
| | | | | | | | | | Remove some pointless code and also fix the return handling for the function since it returns null, not 0 as the comments would suggest. (From OE-Core rev: 6b8d7767ff14345af29d7774b7e16e29c3f7fa8e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/qemutestlib: Add better process debugging and fix process group issueRichard Purdie2013-03-191-5/+20
| | | | | | | | | | | In single testing with a shutdown scenario the processes are cleaned up correctly but the manual cleanup fall back used for a minimal image do not work properly. This patch fixes the kill commands to revert to non-process groups, fixing the hung process issues that were occuring. (From OE-Core rev: 6a0134fd4f1b64ef788be0791bd655dc7703d505) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: avoid unnecessary early expansion with :=Christopher Larson2013-03-192-6/+6
| | | | | | | | | bitbake handles immediate expansions of LAYERDIR for us automatically. (From meta-yocto rev: ee59f1ec94ba8474876603dad1ab32d131227f49) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu-testlib: Add python helper and simplify shellRichard Purdie2013-03-193-158/+117
| | | | | | | | | | | | | | | | | | The current code has a race since it greps for *any* qemu process running, even if it isn't the one we started. This leads to some sanity tests potentially failing on machines where multiple sets of sanity tests are running. To resovle this and some other ugly code issues, add a python script to accurately walk the process tree and find the qemu process. We can then replace all the shell functions attempting this which happen to work in many cases but not all. Also clean up some of the error handling so its more legible. (From OE-Core rev: b9e052ed6b604f0049bcfa968a57f15d6e3d6395) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mkefidisk.sh: create a proper ESPKoen Kooi2013-03-181-0/+8
| | | | | | | | | | | | | The script was creating a FAT fs with EFI files in it, but wasn't setting the GPT GUID. Using 'gummiboot install' natively failed because of the missing GPT GUID, so fix that. While we're there also set the name to "EFI System Partition". (From OE-Core rev: 203ca80ee27948e2c68aab8ea48e51ff1c1157d5) Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Acked-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: add machine-user-features.scc to templatesTom Zanussi2013-03-1736-0/+30
| | | | | | | | | | Add the user-features.scc files needed by the new kernel feature support in yocto-kernel. (From meta-yocto rev: 0ef493fbbe412b6e30fc60b892ba6c2e5664307f) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-kernel: add support for destroying recipe-space kernel featuresTom Zanussi2013-03-173-0/+133
| | | | | | | | | | | | Add a yocto-kernel command allowing users to destroy a recipe-space kernel feature local to a particular BSP. The removed feature is subsequently no longer available for the normal feature addition and removal yocto-kernel commands. (From meta-yocto rev: faa18f56d9412694f2c8e0b0c09e751cb7f3a743) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-kernel: add support for creating recipe-space kernel featuresTom Zanussi2013-03-173-1/+162
| | | | | | | | | | | | | Add a yocto-kernel command allowing users to create a recipe-space kernel feature local to a particular BSP. The new feature is subsequently available for the normal feature addition and removal yocto-kernel commands used with features defined in the meta branch of linux-yocto kernel repos. (From meta-yocto rev: 13abcd93b9e1591bc45ff5f9eb17b8feb9ac9ae5) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-kernel: add support for printing kernel feature descriptionsTom Zanussi2013-03-173-0/+105
| | | | | | | | | | Add a yocto-kernel command allowing users to print the description and compatibility of a given kernel feature. (From meta-yocto rev: 73b4f1a8d156af6810cdde3af672d6286a7071e7) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-kernel: add support for listing available kernel featuresTom Zanussi2013-03-173-1/+164
| | | | | | | | | | | | Add a yocto-kernel command allowing users to list all the kernel features available to a BSP. This includes the features contained in linux-yocto meta branches as well as recipe-space features defined locally to the BSP. (From meta-yocto rev: 12f3af8d92456ad9212170decdbe102fc78b58f6) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-kernel: add support for kernel feature add/rm/listTom Zanussi2013-03-173-1/+267
| | | | | | | | | | | | | | | | | | | | Add yocto-kernel commands allowing users to add, remove, and list kernel features with respect to a given BSP. Features managed by these commands modify a special machine-user-features.scc file associated with the kernel recipe (.bbappend) of a yocto-bsp-generated BSP. This is analagous to the implementation of similar support for bare config items and patches already implemented for yocto-bsp-generated BSPs. Future patches will add support for providing a list of eligible features as defined by linux-yocto kernels and locally-defined (recipe-space) kernel features. (From meta-yocto rev: ae68d906c5c9854f2cd7ee0870556fbfbd7d94d0) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: upgrade i386 template with emgd 1.16Tom Zanussi2013-03-173-7/+7
| | | | | | | | | Along with related changes. (From meta-yocto rev: 6e93c881e2323b57f5b102db3b2b54220a06a1b6) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: add support for linux-yocto-devTom Zanussi2013-03-1712-24/+181
| | | | | | | (From meta-yocto rev: 637104794a5646869d03ff5851d94199b1584dcf) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: add support for tinyTom Zanussi2013-03-1712-0/+245
| | | | | | | (From meta-yocto rev: 61a7cfb5f552586dd13fc553305e334ac53a8ce6) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: update linux-yocto-rt_3.4 .bbappendsTom Zanussi2013-03-176-73/+18
| | | | | | | | | | Simplify by removing unnecessary KMACHINE/KBRANCH and SRC_URI items. Also simplify machine-preempt-rt.scc (From meta-yocto rev: b9973f7761b86e3d4571fe5582759e5405e1d7b4) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: update machine-preempt-rt.sccTom Zanussi2013-03-176-30/+17
| | | | | | | | | Simplify machine-standard.scc for all the templates. (From meta-yocto rev: ad0d944698a854a281d0beea1c87a0600e98ccbd) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: update 3.4 .bbappendsTom Zanussi2013-03-176-73/+18
| | | | | | | | | Simplify by removing unnecessary KMACHINE/KBRANCH and SRC_URI items. (From meta-yocto rev: d1224846e5ff6c101bf50011d5d3314cbbd81f61) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: update machine-standard.sccTom Zanussi2013-03-171-19/+1
| | | | | | | | | Simplify machine-standard.scc for all the templates. (From meta-yocto rev: ac8ec04c50bc8dbf716ff5746c8942566fd5c2bf) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/lib/bsp/engine.py: add preempt-rt and tiny to map_standard_kbranch()Tom Zanussi2013-03-171-0/+36
| | | | | | | | | Update map_standard_kbranch() with preempt-rt and tiny variants. (From meta-yocto rev: 48233b051b0599ee745d0b8d24863a08e7440d6a) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: use map_standard_branch()Tom Zanussi2013-03-173-3/+3
| | | | | | | | | Use map_standard_branch() instead of naming the branch directly. (From meta-yocto rev: 34ec7d4cf53f82adb8de61969d0981344f9a1d87) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/lib/bsp/engine.py: update map_standard_kbranch()Tom Zanussi2013-03-171-8/+6
| | | | | | | | | | Update map_standard_kbranch() to be consistent with the new changes in meta naming and remove obsolete standard/default mapping. (From meta-yocto rev: 40998ba44e1a4ebb1c165cab1a250025041e0da0) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: update default custom kernelTom Zanussi2013-03-171-4/+4
| | | | | | | | | | Update the default custom kernel to 3.8.y, the current stable kernel available at this point. (From meta-yocto rev: f10f30bf77ee0571c1b5edc083833c5267d013d6) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* yocto-bsp: add 3.8/remove 3.2 kernel from templatesTom Zanussi2013-03-1724-421/+110
| | | | | | | | | For Yocto 1.4, 3.8 is the preferred kernel and 3.2 is obsolete. (From meta-yocto rev: 5b07921319901a3709492c43397c57bbd2201585) Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mkefidisk.sh: Cope with translations and modelnames with 'Disk' in it.Koen Kooi2013-03-101-1/+3
| | | | | | | | | | | | | | | The script greps for 'Disk', which doesn't work when your crazy Dutch distro has parted call it 'Schijf', so force LANG=C. The second problem is that 'Disk' might be a substring in the Model entry: [root@Angstrom-F16-vm-rpm contrib] # parted /dev/sdc unit mb print Model: SanDisk SDDR-113 (scsi) Disk /dev/sdc: 3905MB (From OE-Core rev: 2e404930f6fc7d818d2f429793e84bce77163afd) Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake-whatchanged: print what is about to happenRobert Yang2013-03-071-0/+339
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Contents: - Summary - Usage - Implementation summary - Output - TODO * Summary: This is used for printing what is about to happen between the current and last builds, for example: $ bitbake core-image-sato # Edit some recipes $ bitbake-whatchanged core-image-sato The changes will be printed. * Usage: bitbake-whatchanged [[opts] recipe] * Implementation summary: - Use the "STAMPS_DIR=<path> bitbake -S recipe" to generate the new stamps, compare these stamps to the one in the old stamps dir (tmp/stamps), so we will get what are changed. - When the "-v" (verbose) is not specified: > Figure out the newly added tasks > Figure out the PV (including PE) and PR changed tasks > The left tasks are the ones that the "Dependencies" changed tasks - When "-v" is specified: > Figure out the newly added tasks > Use bb.siggen.compare_sigfiles to figure out the details * Output, for example (core-image-sato with different git tags) and with recipes upgraded): - without "-v": Figuring out the STAMPS_DIR ... Generating the new stamps ... (need several minutes) === Newly added tasks: (5 tasks) core-image-sato: do_configure do_populate_lic do_install do_rootfs do_compile # Note: This is because the "bitbake -S" always generate the sigdata for # do_compile, do_rootfs and other task, we may need fix this from "bitbake -S" === PV changed: (130 tasks) alsa-utils: 1.0.25 -> 1.0.26 cross-localedef-native: 2.16 -> 2.17 eglibc-initial: 2.16 -> 2.17 [snip] === Dependencies changed: (3593 tasks) busybox: do_package do_package_write do_build do_packagedata do_populate_sysroot do_install do_compile do_package_write_rpm do_configure do_populate_lic atk-native: do_compile do_package_write_rpm do_package do_configure do_populate_sysroot do_install do_populate_lic do_patch do_packagedata do_build do_package_write do_unpack [snip] === Summary: (3728 changed, 1134 unchanged) Newly added: 5 PV changed: 130 PR changed: 0 Dependencies changed: 3593 Removing the newly generated stamps dir ... - with "-v": === Newly added tasks: (5 tasks) core-image-sato: do_configure do_populate_lic do_install do_rootfs do_compile === The verbose changes of glib-2.0-native.do_do_install: Hash for dependent task virtual:native:glib-2.0_2.34.3.bb.do_compile changed from bab8b8dd95be1b83dcec93f755b1812b to 70f746df7809acaa52de204b0685abb4 [snip] === Summary: (3728 changed, 1134 unchanged) Newly added: 5 Dependencies changed: 3723 Removing the newly generated stamps dir ... * TODO - It seems that the "bitbake -S core-image-sato" has bugs, it would always report errors, but doesn't fatal errors - The gcc-cross' stamps are in tmp/stamps/work-shared, but the "bitbake -S" doesn't put the stamps in work-shared. - The "bitbake -S" always generates the sigdata for image recipe's do_compile, do_install and other tasks, we may need fix this from "bitbake -S". - Print the ones which can be installed from the sstate. [YOCTO #1659] (From OE-Core rev: 8783fcc23ccbd829ecb0dc59cf71ee44376094cc) 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>
* bitbake.conf: add STAMPS_DIR for constructing STAMPRobert Yang2013-03-071-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | Add STAMPS_DIR for constructing STAMP, the defination of STAMP is: STAMP = "${TMPDIR}/stamps/${MULTIMACH_TARGET_SYS}/${PN}/${EXTENDPE}${PV}-${PR}" We can only change the TMPDIR if we want to change the STAMP's location, but the bb_cache.dat would be regenerated if TMPDIR changes, so add STAMPS_DIR for constructing it, and add it to the BB_ENV_EXTRAWHITE, this is very usefull for the "bitbake -S", since then it can be run by: STAMPS_DIR=<path> bitbake -S <recipe> which will avoid putting the stamps to ${TMPDIR}/stamps. BTW, break the too long BB_ENV_EXTRAWHITE into several lines. [YOCTO #1659] (From OE-Core rev: ce732c04b3ac06633e20efa8799c4189abfd41b3) 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>
* qemuimage-tests/dmesg: Add exception for error message on qemuarm with 3.8 ↵Richard Purdie2013-03-021-1/+3
| | | | | | | | | | | | kernel With 3.8 kernels we get a harmless error message during kernel boot. For now we can ignore. This allows the tests to pass and ensures we can merge the 3.8 kernel. (From OE-Core rev: da1e094c407353af2ab230c4867c9d8fd68e3161) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate-cache-management.sh: don't hardcode available sstate_suffixesHongxu Jia2013-02-281-2/+7
| | | | | | | | | | | | | Don't hardcode available sstate_suffixes(it misses `packagedata'), find them dynamically in $sstate_list. [YOCTO #3635] (From OE-Core rev: 26adfcb8c33fe62f5e15c3591efc670d70cbb5b7) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate-cache-management.sh:fix the incorrect usage of option `-d'Hongxu Jia2013-02-281-2/+2
| | | | | | | | | | | | | | The description of option `-d' is not correct in useage. It is used to remove duplicate and debug at the same time. Use option `-D' to control debug info output and the option `-d' to flag remove duplicate. [YOCTO #3635] (From OE-Core rev: fa0b40c233e757fe986aa45798b35b60b89c879f) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate-cache-management.sh: fix remove duplicate failed when multiple archsHongxu Jia2013-02-281-1/+3
| | | | | | | | | | | | | | | | | | | The implementation of `--remove-duplicated' has been modified by the commit: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=0740f82aea92da0195524e37c372f9981e7f5e6d In above commit, sstate cache files with multiple archs are not considered duplicate and don't need to be removed as duplicated any more. Update the description of `--remove-duplicated' in usage to keep consistent with implementation. [YOCTO #3635] (From OE-Core rev: c201fdc2f01f398060cd953a1640a685797d9e64) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/bitbake: Remove all instances of paths to a layer's scripts directory.Franklin S. Cooper Jr2013-02-151-1/+1
| | | | | | | | | | | | | | | | | | | * Currently the assumption is made that only oe-core can include a scripts directory. * However, when other layers create a scripts directory the bitbake script freaks out causing a infinite recursive loop until it crashes. * Simply changing the regular expression to remove all instances of scripts path instead of just the first one fixes this problem. [Yocto Bug 3872] (From OE-Core rev: 9b445cc39604223b0cfb21d28f748a86ff4cdf68) Signed-off-by: Franklin S. Cooper Jr <fcooper@ti.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Python: Add missing dependency "textutils" to "io" packageMiLo2013-02-141-1/+1
| | | | | | | | | | | | | | | | | | | | | | Modify the include file and script to generate a missing RDEPENDS. Install python on target with python-io. Import ssl: Python 2.7.3 (default, Feb 9 2013, 16:04:35) [GCC 4.7.2] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import ssl Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python2.7/ssl.py", line 58, in <module> ImportError: No module named textwrap Installing python-textutils solves the issue. (From OE-Core rev: 900ae881c3483eea36aa0be456b93f92980f4924) Signed-off-by: MiLo <milo-software@users.sourceforge.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* scripts/qemuimage-testlib: Use wide option to ps callsMichael Halstead2013-02-131-5/+5
| | | | | | | | | | | | | | | Forcing ps to display unlimited column width allows the qemu IP address to be discovered during sanity testing when the command line is extremely long. This seems to fix the sanity testing problem on AB05 which was recently updated to OpenSUSE 12.2. I'm not sure what about qemu or process listing is different on that distribution but this simpile fix seems to work and my help on other distro's as well. (From OE-Core rev: 4cea35cc4e4ed8e68cd117825b1dd4ef1be768c2) Signed-off-by: Michael Halstead <michael@yoctoproject.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add separate directory for postinstall interceptsLaurentiu Palcu2013-02-134-0/+66
| | | | | | | | | | | | | | | | | | | | | The scripts/postinst-intercepts will contain all postinstall hooks that we need to run after all packages have been installed. If one wants to install such a postinst hook, all it needs to do is put the hook in this directory and, from the package postinstall scriptlet, call: postinst_intercept <hook_name> <package_name> <var1=...> ... This will, practically, add the package_name in the list of packages that need the hook to run and, also, set any variables that would be needed in the hook. For example, variables like ${libdir}, ${bindir}, etc. that might depend on distribution can be passed on to the script in this way. (From OE-Core rev: 0ef538d75c2f3921a2fcbe6ca1deed5525b276cc) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* relocate_sdk.py: allow relocate_sdk.py to work with python 2.4.xJason Wessel2013-02-121-13/+13
| | | | | | | | | | | | | | Avoid the chicken / egg problem of an SDK that provides a working python but requires that version of python to extract itself. The RHEL 5.x systems and some other enterprise Linux systems ship with python 2.4.x as the default python. We need to at least be able to extract work executables even if we never use the the host provided python again. (From OE-Core rev: e1d42db8749b0b965ddc6cfba4f3b93ee96ed4f4) Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* relocate_sdk.py: Fix corruption of sdk binariesJason Wessel2013-02-121-2/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | There are two cases of corruption that the relocate_sdk.py was not correctly dealing with. 1) SDK Extras should be left alone Extra external binaries included in an SDK that were linked against the host's version of /usr/lib/ld-so.so should not get a relocation applied. In the case that was discovered these were LSB compliant binaries that already worked on many hosts. 2) If the interp section is too small generate an error In the case of the qemu user code, it was using its own .ld file to link the executables which overrides the default in the nativesdk binutils. This generated host executables which had a interp section that was too small to relocate. Now the relocate_sdk.py will print an error and continue on such that the error can be fixed by a developer without having to do the difficult task of debugging why it is crashing or not loading correctly. (From OE-Core rev: 3752a9c6d772b39bbe04d62ef4d3527b4c7198c1) Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-git-proxy*: Remove previous git proxy solutionsDarren Hart2013-02-113-3015/+0
| | | | | | | | | | | | The new oe-git-proxy should address all git proxying needs, remove the previous scripts. V2: Separate the removal of the old scripts into their own patch (From OE-Core rev: 75738ac47b9ca11daa94820c9c5f829937397da7) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-git-proxy: Use socat instead of BSD ncDarren Hart2013-02-111-32/+27
| | | | | | | | | | | | | | BSD nc was commonly available on the current distros until Fedora 18 appears to have dropped it. socat appears to be a reasonable replacement with availability on Fedora and Ubuntu and going back some time as well. Update the script to use the socat syntax. Simplify the logic a bit by using exec for the no-proxy-needed cases. (From OE-Core rev: 795b1ea370b8a1d9152c171a50e80bd0b4b8dc60) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-git-proxy: Add a new comprehensive git proxy scriptDarren Hart2013-02-111-0/+138
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | oe-git-proxy.sh is a simple tool to be used via GIT_PROXY_COMMAND. It uses BSD netcat to make SOCKS5 or HTTPS proxy connections. It uses ALL_PROXY to determine the proxy server, protocol, and port. It uses NO_PROXY to skip using the proxy for a comma delimited list of hosts, host globs (*.example.com), IPs, or CIDR masks (192.168.1.0/24). It is known to work with both bash and dash shells. V2: Implement recommendations by Enrico Scholz: o Use exec for the nc calls o Use "$@" instead of $* to avoid quoting issues inherent with $* o Use bash explicitly and simplify some of the string manipulations Also: o Drop the .sh in the name per Otavio Salvador o Remove a stray debug statement V3: Implement recommendations by Otavio Salvador o GPL license blurb o Fix minor typo in comment block (From OE-Core rev: 62867f56da0e0904f0108f113324c2432659fbac) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Enrico Scholz <enrico.scholz@sigma-chemnitz.de> Cc: Otavio Salvador <otavio@ossystems.com.br> git-proxy cleanup Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oe-buildenv-internal: Add upper and lower case proxy vars to BB_ENV_EXTRAWHITEDarren Hart2013-02-111-1/+1
| | | | | | | | | | | | | | | | | Applications are inconsistent in their use of upper and lower case proxy variables. Curl, for example, specifies NO_PROXY (not no_proxy) in the man page (changed in 2009 [1]). Avoid proxy issues by ensuring both the upper and lower case versions of each proxy variable are available in the environment for the fetcher commands. Add FTPS_PROXY and ftps_proxy to the list as well. 1. http://curl.haxx.se/mail/tracker-2009-04/0012.html (From OE-Core rev: 684c6512850ceb108e52af634be98eaacb8351e1) Signed-off-by: Darren Hart <dvhart@linux.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-12 18:28:37 +0000