Op 23 mei 2012, om 14:46 heeft Samuel Stirtzel het volgende geschreven:
> Valgrind supports the armv7 architecture, this patch allows armv7 users to
> build and use Valgrind
>
> This patch was run-tested on a Gumstix Overo (armv7a cortex-a8)
> * The test consisted of running valgrinds memcheck (memory leakage detection),
> * and callgrind (profiling) on a Qt 4 application
>
> Signed-off-by: Samuel Stirtzel <[email protected]>
> ---
> meta/recipes-devtools/valgrind/valgrind_3.7.0.bb | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/meta/recipes-devtools/valgrind/valgrind_3.7.0.bb
> b/meta/recipes-devtools/valgrind/valgrind_3.7.0.bb
> index d7c7b24..0998f72 100644
> --- a/meta/recipes-devtools/valgrind/valgrind_3.7.0.bb
> +++ b/meta/recipes-devtools/valgrind/valgrind_3.7.0.bb
> @@ -23,13 +23,16 @@ SRC_URI[md5sum] = "a855fda56edf05614f099dca316d1775"
> SRC_URI[sha256sum] =
> "5d62c0330f1481fe2c593249192fa68ff454c19c34343978cc9ce91aa324cbf6"
>
> 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"
we should already be passing --host through autotools.bbclass. Does the
configure have a special check? I've seen a few projects that insist on the
-none- TARGET_VENDOR for no good reason :(
> EXTRA_OEMAKE = "-w"
> PARALLEL_MAKE = ""
>
> FILES_${PN}-dbg += "${libdir}/${PN}/*/.debug/*"
> RRECOMMENDS_${PN}_powerpc += "${TCLIBC}-dbg"
> RRECOMMENDS_${PN}_powerpc64 += "${TCLIBC}-dbg"
> +RRECOMMENDS_${PN}_armv7a += "libc6-dbg"
${TCLIBC}-dbg ?
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
