linux/poky.git/meta/recipes-devtools/pseudo, branch 1.6_M3.final

meta/recipes: Remove virtclass references

2014-02-13T11:41:21+00:00

The virtclass overrides will go away at some point (apart from the multilib one). Change them all to class-xxx instead since people enjoy copy and pasting them. (From OE-Core rev: d1c073d2813bd913617990cd047507353ea0c09e) Signed-off-by: Richard Purdie

Replace one-line DESCRIPTION with SUMMARY

2014-01-02T12:50:18+00:00

A lot of our recipes had short one-line DESCRIPTION values and no SUMMARY value set. In this case it's much better to just set SUMMARY since DESCRIPTION is defaulted from SUMMARY anyway and then the SUMMARY is at least useful. I also took the opportunity to fix up a lot of the new SUMMARY values, making them concisely explain the function of the recipe / package where possible. (From OE-Core rev: b8feee3cf21f70ba4ec3b822d2f596d4fc02a292) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

recipes: Remove PR = r0 from all recipes

2013-10-30T14:52:04+00:00

Remove all PR = "r0" from all .bb files in oe-core. This was done with the command sed -e '/^PR.*=.*r0\"/d' recipes*/*/*.bb -i We've switching to the PR server, PR bumps are no longer needed and this saves people either accidentally bumping them or forgetting to remove the lines (r0 is the default anyway). (From OE-Core rev: 58ae94f1b06d0e6234413dbf9869bde85f154c85) Signed-off-by: Richard Purdie

pseudo: fix library path in FILES_${PN}

2013-10-29T10:41:38+00:00

libpseudo.so is always installed into ${prefix}/lib/, not ${libdir}, so fix these paths; and skip libdir WARN_QA checking to ignore the warning in 64bit and multilib enabled system (From OE-Core rev: 47c7850c025994685aa1811057f4f9a5f0f2a3ae) Signed-off-by: Roy Li Signed-off-by: Richard Purdie

pseudo: Fix race problems

2013-09-30T21:56:19+00:00

There is a potential issue with the fastop code in pseudo since a process may exit and allow some other function to run before the server has processed the commands run by the process. Issues have been see with unpredictable file permissions. To avoid this, we ping the server before exitting which guarantees it has processed the current command queue. The patch was written by peter.seebach@windriver.com [YOCTO #5132] (From OE-Core rev: a8a1f12c51ffdca011db194894fd7d14c119fb09) Signed-off-by: Richard Purdie

pseudo: warn twice if the 32-bit toolchain appears broken

2013-09-26T16:00:05+00:00

Putting a warning at the top of do_compile is useful but not everyone reads the file from beginning to end, so use a trap to put the message at the bottom too. [ YOCTO #4919 ] (From OE-Core rev: 51950fcbe4b98bdbb8b3dde88a8729e540d9609f) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

pseudo: use bbnote/bbwarn instead of echo

2013-09-26T16:00:05+00:00

In the future bbnote/bbwarn will be integrated into bitbake's logging, so use those functions instead of echo directly. (From OE-Core rev: 4933d7ae45d88090191c8ea07fd109ed34925e2d) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

pseudo: force NO32LIB to true for nativesdk

2013-09-22T11:19:42+00:00

The exported SDK only needs simulated root privileges for specific tasks, such as the user-mode NFS server or rootfs extraction, and oe-core does not support multilib builds in the generated SDK, so it is neither necessary nor possible to build a 32-bit libpseudo.so for a 64-bit SDK. [YOCTO #5135] (From OE-Core rev: 908b179b798704db74c886ec4c70c0942b09cb00) Signed-off-by: Randy MacLeod Signed-off-by: Richard Purdie

pseudo: fix memory leak and missed privilege drop

2013-09-06T22:03:20+00:00

qemu.bbclass adds PSEUDO_UNLOAD=1 in qemu_run_binary to avoid reference to pseudo functions that may not exist in the target environment. This patch detects the addition of that variable within the environment to which the call applies, even if not present in the parent environment. As a side effect it fixes a memory leak. [YOCTO #4843] (From OE-Core rev: 9ea32ef507c914f906b3dcc0bb29813a4e0dacba) Signed-off-by: Peter A. Bigot Signed-off-by: Richard Purdie

remove the unnecessary protocol parameters

2013-08-30T15:23:46+00:00

It's not necessary to specify the protocol parameter when it's the default protocol for the fetcher, e.g. the default protocol for git fetcher it git, "protocol=git" isn't needed. (From OE-Core rev: a2bab241c64428d5109c3c5ac5de4463fbad70c5) Signed-off-by: Jackie Huang Signed-off-by: Richard Purdie