From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Building Valgrind
Date: Thu, 17 May 2012 15:21:05 +0100 [thread overview]
Message-ID: <4FB50951.4000503@communistcode.co.uk> (raw)
I am attempting to build Valgrind with mu very minimal package compiling
experience, and unsurprisingly for such a complex program I am stuck! I
will be happy to submit it to meta-oe once it is building and believe it
would be very useful now that it supports ARM (and MIPS to some extent
apparently). So, my progress so far:
From what I can gather the autoconf class is passing --warning=cross
which it doesn't understand... I'm really not very experienced at this! :-)
bb file:
DESCRIPTION = "Valgrind"
HOMEPAGE = "http://www.valgrind.org"
LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=c46082167a314d785d012a244748d803"
inherit autotools gettext pkgconfig
SRC_URI = "http://valgrind.org/downloads/valgrind-${PV}.tar.bz2"
SRC_URI[md5sum] = "a855fda56edf05614f099dca316d1775"
error:
DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common',
'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common']
ERROR: Function failed: do_configure (see
/home/jack/angstrom.git/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/valgrind-3.7.0-r0/temp/log.do_configure.14418
for further information)
automake (GNU automake) 1.11.2
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 or later
<http://gnu.org/licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by Tom Tromey <tromey@redhat.com>
and Alexandre Duret-Lutz <adl@gnu.org>.
AUTOV is 1.11
NOTE: Executing autoreconf --verbose --install --force
--exclude=autopoint
-I/home/jack/angstrom.git/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/share/aclocal-1.11
-I
/home/jack/angstrom.git/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/valgrind-3.7.0-r0/valgrind-3.7.0/aclocal-copy/
autoreconf: Entering directory `.'
autoreconf: configure.in: not using Gettext
autoreconf: running: aclocal -I
/home/jack/angstrom.git/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/share/aclocal-1.11
-I
/home/jack/angstrom.git/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/valgrind-3.7.0-r0/valgrind-3.7.0/aclocal-copy/
-I
/home/jack/angstrom.git/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/share/aclocal-1.11
-I
/home/jack/angstrom.git/build/tmp-angstrom_2010_x-eglibc/work/armv7a-angstrom-linux-gnueabi/valgrind-3.7.0-r0/valgrind-3.7.0/aclocal-copy/
--force --warnings=cross
aclocal: unknown warning category `cross'
aclocal: aclocal: file
`/home/jack/angstrom.git/build/tmp-angstrom_2010_x-eglibc/sysroots/x86_64-linux/usr/share/aclocal/gsettings.m4'
does not exist
autoreconf: aclocal failed with exit status: 1
ERROR: autoreconf execution failed.
~
Thanks in advance!
Regards,
Jack.
--
Jack Mitchell (jack@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
next reply other threads:[~2012-05-17 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 14:21 Jack Mitchell [this message]
2012-05-17 14:28 ` Building Valgrind Martin Jansa
2012-05-17 14:31 ` Jack Mitchell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FB50951.4000503@communistcode.co.uk \
--to=ml@communistcode.co.uk \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.