Op 1 mei 2012, om 12:21 heeft Richard Purdie het volgende geschreven: > On Mon, 2012-04-30 at 15:48 -0500, Peter Seebach wrote: >> On Mon, 30 Apr 2012 15:42:44 -0500 >> Mark Hatle <[email protected]> wrote: >> >>> Is the above debugging? (I suspect it is) I suggest the following... >> >> Actually, that one's intentional. I originally did it for debugging, >> but I thought it was super convenient to actually get a list of the CPU >> feature set bitbake thought it was using. We can't tell you whether >> you picked the right features, but we can tell you what they are. >> >> So for instance, with a qemux86 and a core2 lib32: >> >> NOTE: Sanity-checking tuning 'x86-64' (default) features: >> NOTE: checking for conflicts: m64 >> NOTE: checking for conflicts with: m32 >> NOTE: m64: IA32e (x86_64) ELF64 standard ABI >> NOTE: Sanity-checking tuning 'core2' (lib32) features: >> NOTE: m32: IA32 ELF32 standard ABI >> NOTE: core2: Enable core2 specific processor optimizations >> >> I found this really handy, and left it there on purpose. I could take >> it out, and/or move it to somewhere else, but I really do like having >> that information appear. > > I'd change these to debug messages. Users don't need this on the console > on every run. There is already a summary of the active tune options > displayed in the build configuration banner if I remember correctly.
indeed: BB_VERSION = "1.15.1" TARGET_ARCH = "arm" TARGET_OS = "linux-gnueabi" MACHINE = "beagleboard" DISTRO = "angstrom" DISTRO_VERSION = "v2012.05-core" TUNE_FEATURES = "armv7a vfp neon cortexa8" TARGET_FPU = "vfp-neon" _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
