from poking around in packagegroup files, the following observation. first, there's the valgrind recipe itself, which suggests at least armv7a support:
COMPATIBLE_HOST = '(i.86|x86_64|powerpc|powerpc64).*-linux' COMPATIBLE_HOST_armv7a = 'arm.*-linux' inherit autotools EXTRA_OECONF = "--enable-tls" EXTRA_OECONF_armv7a = "--enable-tls -host=armv7-none-linux-gnueabi" EXTRA_OEMAKE = "-w" PARALLEL_MAKE = "" this appears to disagree with what one reads in packagegroup-core-tools-profile.bb, which suggests no arm support whatsoever(?): # valgrind does not work on mips VALGRIND = "valgrind" VALGRIND_libc-uclibc = "" VALGRIND_mips = "" VALGRIND_arm = "" <-- ??? VALGRIND_aarch64 = "" note also that the comment doesn't even match what follows, which is quite common in that very file, as in: # lttng-tools, lttng-modules and babeltrace all depend on liburcu # which currentl doesn't build on mips LTTNGTOOLS = "lttng-tools" LTTNGTOOLS_mips = "" LTTNGTOOLS_aarch64 = "" and, finally, there's valgrind 3.8.0, which now apparently has mips support: http://valgrind.org/info/platforms.html so just some contradictory info scattered around. rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
