linux/poky.git/meta/recipes-devtools/pseudo, branch 1.4_M5.final

Update pseudo to 1.5.1

2013-03-01T13:03:28+00:00

pseudo 1.5's enable-force-async works great, unless you use a host where, inexplicably, stat(2) reports inconsistent and changing values for a file's size or times for some time unless a file has been fsynced, in which case you might want a way to cause an fsync to work. Also noticed that some recent changes never made it into the docs, so I did a little cleanup there. And changed the way NDEBUG suppresses pseudo's debug messages, so arguments to them with possible side effects (like calls into functions in another translation unit) can be omitted, which should drastically reduce computational time if anyone ever uses NDEBUG. (From OE-Core rev: 150174d52adefdefe62e2ed0598665481591e4c2) Signed-off-by: Peter Seebach Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

pseudo.inc: pseudo 1.5 uprev, support extra config flags

2013-02-19T16:47:35+00:00

The pseudo 1.5 update is a moderately experimental set of changes which ought to improve performance. With these changes, pseudo uses an in-memory sqlite database which is lushed on exit, the protocol is changed to reduce waiting for server responses, and pseudo can suppress any and all fsync/fdatasync type operations. This last feature is optional, and not on by default, so we need to pass in an extra configure argument, but that argument wouldn't be known to an older configure, so... Enter PSEUDO_EXTRA_OPTS which is passed to configure, and which pseudo_1.5.bb sets by default to "--enable-force-async". (I haven't added it in pseudo_git.bb, but maybe it should be changed; I'm not quite as sure there.) The justification for these changes is that, for most of the real-world build cases I deal with, they produce a 25% or more reduction in the build time of a project. This increases when a system is heavily loaded. (From OE-Core rev: 79ddb0c33401da442dbaa8e0d73ebacf297d9185) Signed-off-by: Peter Seebach Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

pseudo_1.4.5.bb: Finish fixing linkat()

2013-02-13T21:31:37+00:00

The 1.4.4 fix replaced possible double-prepending of chroot paths with possible non-prepending of chroot paths. After significant evaluation, have settled on a single prepending of the chroot path as a workable compromise. (From OE-Core rev: a79597994e3f680e34a1a45fb37d76977903ded5) Signed-off-by: Peter Seebach Signed-off-by: Richard Purdie

pseudo_git.bb: Bump to pseudo 1.4.4.

2013-02-13T16:52:30+00:00

The pseudo 1.4.2 linkat() implementation had a broken edge case in which you could end up with chroot paths being doubled when using plain link() calls instead of linkat() calls. (From OE-Core rev: c70443ef21713d805012ef839e3fac04de8eadd2) Signed-off-by: Peter Seebach Signed-off-by: Richard Purdie

pseudo.inc: Fix sqlite libdir again, pseudo 1.4.3

2013-02-08T14:50:36+00:00

This updates to pseudo 1.4.3. Changes: 1. A couple of minor tweaks to reduce difficulties using SDKs built on slightly more recent machines on older machines; specifically, avoiding getting @GLIBC_2.7 symbol references for sscanf(), fscanf(), and open2(). 2. Revision of the logic determining the library directory to use for sqlite's library files. The latter is a source of difficulty because it's come up a few times that we may want pseudo to use lib64 for libpseudo.so, but bitbake's usual setup would have libsqlite3.a in lib regardless of bit width. Cleaned up previous design a bit by providing a distinct setting for sqlite-lib, which defaults to the same library directory used for other things. Adjusted build to use this new setting. (This ends up being ${baselib}; on targets, that might not be lib, but for native builds it generally is, and for SDK builds it appears to do the right thing.) Testing: Successful build of meta-toolchain for both 64-bit and 32-bit SDKMACHINE, and builds with NO32LIBS = "0" also succeeded. Also builds for multilib targets. (From OE-Core rev: ae8811bb26fba2e71d7280f6d6c4f5cec6a2871b) Signed-off-by: Peter Seebach Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

recipes-devtools: replace virtclass-native(sdk) with class-native(sdk)

2012-11-02T16:18:29+00:00

The overrides virtclass-native and virtclass-nativesdk are deprecated, which should be replaced by class-native and class-nativesdk. [YOCTO #3297] (From OE-Core rev: bb67ddeb2eed3e25c626a279ef53a7e8c7bfe6f2) Signed-off-by: Robert Yang Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

pseudo_1.4.1.bb: update to pseudo 1.4.1, fixing 32-bit host problems

2012-09-14T08:50:29+00:00

There were a number of cases where pseudo used plain old stat() to get dev/inode data for files; on 32-bit hosts, this could fail if the files were over 2GB, causing pseudo to prevent removing of large files. This is fixed in 1.4.1. (From OE-Core rev: 056eddc4299d10ddafe0da3dc768bd80d0c1b96b) Signed-off-by: Peter Seebach Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

pseudo: Fix pseudo-native rebuild when triggered by dep change

2012-08-19T09:45:59+00:00

When NO32LIBS = 0, building 32-bit version of pseudo-native and building on a 64-bit host -- if the build was triggered by a dependency change on something pseudo uses, the build could fail due to left over files from the previous build. Fix this by ensuring we run make distclean (and ignoring any failure codes) to ensure we start over. (From OE-Core rev: 30ae7320265efe039730cd2faf7bd86a264412ed) Signed-off-by: Mark Hatle Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

pseudo.inc/pseudo_1.4.bb: update pseudo to 1.4

2012-07-29T09:16:16+00:00

This update replaces the half-baked --arch logic with the use of $CFLAGS to pick compiler flags, on the grounds that it makes a lot more sense for the build system to pick flags than for pseudo to try to guess what they should be; this should allow pseudo to at least compile for targets, and possibly run on them. This doesn't solve the problem of guessing how to forcibly build the 32-bit variant on hosts, because we really don't have a general solution for that. There's no idiom for "given this set of compiler flags and this architecture, what flags would you use to request a 32-bit compile instead?" So we basically ignore that for now. If someone comes along trying to use the build system to build pseudo-native on a 64-bit host that also supports 32-bit binaries and isn't x86, we will revisit this. (From OE-Core rev: 711fcb4f10e2cefd7ff6e1921d87d1cad840d0c8) Signed-off-by: Richard Purdie

pseudo: Update to 1.3.1 (fixing chroot crash)

2012-07-09T15:58:58+00:00

Yocto bug #2639. If a chroot path was long, expanding absolute paths within the chroot path could overrun a buffer. (From OE-Core rev: 282cbf7002112f6b58ca1ee070c0b1285b838db7) Signed-off-by: Peter Seebach Signed-off-by: Richard Purdie