Mirror of git.yoctoproject.org/poky https://git.enea.com/cgit/linux/poky.git/atom?h=dylan 2012-09-14T08:50:29+00:00 2012-09-14T08:50:29+00:00 Peter Seebach peter.seebach@windriver.com 2012-09-13T18:29:59+00:00 urn:sha1:4bb2ce4f30ed1d466577c9cd65a8df5e51ade412 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 <peter.seebach@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2012-07-29T09:16:16+00:00 Peter Seebach peter.seebach@windriver.com 2012-07-27T21:54:48+00:00 urn:sha1:3d164f74fdb994c08c7e3f6d93cd4e1959b4eb7e 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 <richard.purdie@linuxfoundation.org>