From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-10-05
Date: Mon, 06 Oct 2014 15:13:13 -0300 [thread overview]
Message-ID: <5432DBB9.8030507@zacarias.com.ar> (raw)
In-Reply-To: <20141006094333.211d8a76@free-electrons.com>
On 10/06/2014 04:43 AM, Thomas Petazzoni wrote:
>> powerpc | slang-2.3.0 | NOK | http://autobuild.buildroot.net/results/ec9f1d7680aa50357d9a6646cef610dcaa1e8041/
>
> Missing termcap library. Gustavo, maybe ?
Hi.
I'll give this a look, from a quick one "there's no termcap lib" so the
solution would be to just nuke support for it (it tries to automatically
detect it).
>> powerpc | valgrind-3.10.0 | NOK | http://autobuild.buildroot.net/results/3fe67d9760abbb5c9fbcabf8672ec537a4bffa71/
>> powerpc | valgrind-3.10.0 | NOK | http://autobuild.buildroot.net/results/31d4cffaf0541c5dcb21de609dc97c0d303c2111/
>
> vgdb-invoker-ptrace.c: In function 'waitstopped':
> vgdb-invoker-ptrace.c:319:24: error: 'PTRACE_GETSIGINFO' undeclared (first use in this function)
> res = ptrace (PTRACE_GETSIGINFO, pid, NULL, newsiginfo);
> ^
>
> Missing uClibc definitions it seems. Gustavo ?
ptrace support for powerpc is incomplete in uclibc (same problem that
affected enlightenment in commit 37acd25ee1376de5734415ac60be16991ee6d150).
I'll try to work around it even though patches to fix it are already in
upstream uclibc/uclibc-ng since it won't cover external toolchains.
Regards.
next prev parent reply other threads:[~2014-10-06 18:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-10-05 Thomas Petazzoni
2014-10-06 7:15 ` Yegor Yefremov
2014-10-06 7:43 ` Thomas Petazzoni
2014-10-06 18:03 ` Alexey Brodkin
2014-10-06 18:13 ` Gustavo Zacarias [this message]
2014-10-06 19:14 ` Bernd Kuhls
2014-10-06 19:22 ` Matthew Weber
2014-10-06 19:44 ` Thomas Petazzoni
2014-10-06 19:47 ` Matthew Weber
2014-10-06 20:11 ` Alexey Brodkin
2014-10-06 20:20 ` Matthew Weber
2014-10-06 20:28 ` Alexey Brodkin
2014-10-06 20:41 ` Matthew Weber
2014-10-08 1:06 ` Matthew Weber
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=5432DBB9.8030507@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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