From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/trinity: New package
Date: Wed, 8 Oct 2014 10:44:17 +0100 [thread overview]
Message-ID: <54350771.9000208@imgtec.com> (raw)
In-Reply-To: <874mvffs2a.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On 10/07/2014 11:11 PM, Peter Korsgaard wrote:
>>>>>> "Vicente" == Vicente Olivert Riera <Vincent.Riera@imgtec.com> writes:
>
> > Adding the Trinity Linux System call fuzz tester.
> > Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
>
> Thanks, but a quick test build with uClibc fails:
>
> make[1]: Entering directory '/home/peko/source/buildroot/output/build/trinity-c02034ec08d951cde3429905e64afe450cbc47db'
> CC arg-decoder.o
> CC blockdevs.o
> CC child.o
> CC debug.o
> CC devices.o
> debug.c:5:22: fatal error: execinfo.h: No such file or directory
> compilation terminated.
> Makefile:96: recipe for target 'debug.o' failed
> make[1]: *** [debug.o] Error 1
> make[1]: *** Waiting for unfinished jobs....
> make[1]: Leaving directory '/home/peko/source/buildroot/output/build/trinity-c02034ec08d951cde3429905e64afe450cbc47db'
>
> execinfo.h is only available if uClibc is built with
> UCLIBC_HAS_BACKTRACE=y (which it isn't by default).
>
> Perhaps the backtrace() stuff can get #ifdef'ed out if not available?
It looks like a change to be made upstream. Maybe it needs to include a
header check in the configure.sh script, then defining a macro if the
header is present, and then modify the source code to take that macro
into account to do things like "#ifdef USE_EXECINFO"...
So, what do you propose by now for the Buildroot package? Disabling it
for uClibc until upstream fixes that?
--
Vincent
next prev parent reply other threads:[~2014-10-08 9:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 11:21 [Buildroot] [PATCH] package/trinity: New package Vicente Olivert Riera
2014-10-07 22:11 ` Peter Korsgaard
2014-10-08 9:44 ` Vicente Olivert Riera [this message]
2014-10-08 9:58 ` Peter Korsgaard
2014-10-08 10:01 ` Vicente Olivert Riera
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=54350771.9000208@imgtec.com \
--to=vincent.riera@imgtec.com \
--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