From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2016-08-29
Date: Wed, 31 Aug 2016 21:00:02 +0200 [thread overview]
Message-ID: <20160831210002.356770b2@free-electrons.com> (raw)
In-Reply-To: <CAMduVEcsMc8AzLkJNh7FfZgUYejpk17mY+1cOPPf_TrgvPnT3A@mail.gmail.com>
Hello,
On Wed, 31 Aug 2016 19:51:44 +0200, Wojciech Zabolotny wrote:
> Unfortunately I was not able to reproduce the failed build.
> Compilation of a system for xtensa architecture starting from the
> qemu_xtensa_lx60_defconfig
> with addition of C++ support in the toolchain, jack2 and alsa-utils
> was completed without errors.
Regarding the jack2 build failure on xtensa, I already have the
beginning of a patch to solve it, but more testing is needed. You
probably didn't reproduce the error because you enabled only "jack2",
while the problem only occurs when the dbus support of jack2 is enabled.
> Compilation with "config" taken from
> http://autobuild.buildroot.net/results/2c3/2c3cf6cbdc5e954e5768bff836a02cfb0f3528cf/config
> lead to errors in host-faketime long before jack2 was compiled:
>
> >>> host-faketime v0.9.6 Building
[...]
> libfaketime.c:513:7: error: nonnull argument ?buf? compared to NULL
> [-Werror=nonnull-compare]
> if (buf != NULL)
> ^
What is the gcc version on your host machine?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
parent reply other threads:[~2016-08-31 19:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAMduVEcsMc8AzLkJNh7FfZgUYejpk17mY+1cOPPf_TrgvPnT3A@mail.gmail.com>]
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=20160831210002.356770b2@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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