From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0003774]: valgrind doesn't build for powerpc target
Date: Thu, 17 Jul 2008 03:39:51 -0700 [thread overview]
Message-ID: <0ee499fa8ce0416d26a32d88f2d78d9c@busybox.net> (raw)
The following issue has been CLOSED
======================================================================
http://busybox.net/bugs/view.php?id=3774
======================================================================
Reported By: fabo
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 3774
Category: Architecture Specific
Reproducibility: always
Severity: minor
Priority: normal
Status: closed
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 06-15-2008 03:58 PDT
Last Modified: 07-17-2008 03:39 PDT
======================================================================
Summary: valgrind doesn't build for powerpc target
Description:
then mv -f ".deps/libcoregrind_ppc32_linux_a-readstabs.Tpo"
".deps/libcoregrind_ppc32_linux_a-readstabs.Po"; else rm -f
".deps/libcoregrind_ppc32_linux_a-readstabs.Tpo"; exit 1; fi
In file included from m_debuginfo/readstabs.c:46:
/home/test/build-area/buildroot/buildroot/build_powerpc/staging_dir/usr/include/a.out.h:4:26:
error: linux/a.out.h: No such file or directory
m_debuginfo/readstabs.c: In function
'vgModuleLocal_read_debuginfo_stabs':
m_debuginfo/readstabs.c:123: error: invalid application of 'sizeof' to
incomplete type 'struct nlist'
m_debuginfo/readstabs.c:123: warning: division by zero
m_debuginfo/readstabs.c:126: error: invalid use of undefined type 'struct
nlist'
m_debuginfo/readstabs.c:126: error: dereferencing pointer to incomplete
type
======================================================================
----------------------------------------------------------------------
jacmet - 06-15-08 12:19
----------------------------------------------------------------------
Thanks. There were 2 problems:
- valgrind didn't search kernel headers (fixed in r22355)
- linux/a.out.h wasn't exported from the kernel (fixed in r22354)
Notice that you need to use 2.6.25.x kernel headers for it to work.
Issue History
Date Modified Username Field Change
======================================================================
06-15-08 03:58 fabo New Issue
06-15-08 03:58 fabo Status new => assigned
06-15-08 03:58 fabo Assigned To => buildroot
06-15-08 12:19 jacmet Status assigned => resolved
06-15-08 12:19 jacmet Resolution open => fixed
06-15-08 12:19 jacmet Note Added: 0008244
07-16-08 08:02 bernhardf Status resolved => new
07-17-08 03:39 bernhardf Status new => closed
======================================================================
next reply other threads:[~2008-07-17 10:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 10:39 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-15 19:19 [Buildroot] [buildroot 0003774]: valgrind doesn't build for powerpc target bugs at busybox.net
2008-06-15 10:58 bugs at busybox.net
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=0ee499fa8ce0416d26a32d88f2d78d9c@busybox.net \
--to=bugs@busybox.net \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox