From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-20
Date: Tue, 21 Feb 2017 23:01:19 +0100 [thread overview]
Message-ID: <20170221230119.5750f9cd@gmx.net> (raw)
In-Reply-To: <20170221224804.5f901ab5@free-electrons.com>
On Tue, 21 Feb 2017 22:48:04 +0100, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
Hello Thomas,
> Hello,
>
> On Tue, 21 Feb 2017 22:42:30 +0100, Peter Seiderer wrote:
>
> > > xtensa | qt5base-5.8.0 | NOK | http://autobuild.buildroot.net/results/ce6f506f610434dff1d0eb64644be0200d7c52f6
> >
> > ../3rdparty/double-conversion/include/double-conversion/utils.h:81:2: error: #error Target architecture was not detected as supported by Double-Conversion.
> > #error Target architecture was not detected as supported by Double-Conversion.
> >
> > Tried to compile with 'QT5BASE_CONFIGURE_OPTS += -no-doubleconversion', but gives:
> >
> > Qt Core:
> > DoubleConversion ....................... no
> > Using system DoubleConversion ........ no
> >
> > [...]
> >
> > ERROR: Your C library does not provide sscanf_l or snprintf_l.
> > You need to use libdouble-conversion for double/string conversion.
> >
> > Disable BR2_PACKAGE_QT5_VERSION_LATEST for xtensa (or xtensa/uClibc combination)?
> >
> >
> > Similare failure for arc:
> >
> > > arc | qt5base-5.8.0 | NOK | http://autobuild.buildroot.net/results/fda8a5165cc599adfa4b3cb012916fa4dc38aeca
>
> Or add support to the double-conversion code?
>
> For example, m68k support was contributed upstream:
>
> https://github.com/google/double-conversion/commit/da11179623145f53b204105a93b8bbca431141da
Seems simple ;-), but I think it should be done by someone with access to the target arch who can
run the double-conversion test suite...
>
> But indeed, for the release, disabling unsupported architectures is
> probably best. Can you send a patch?
Can do..., depending on BR2_xtensa or (BR2_xtensa && BR2_TOOLCHAIN_USES_UCLIBC)?
Regards,
Peter
>
> Thanks,
>
> Thomas
next prev parent reply other threads:[~2017-02-21 22:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 7:29 [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-20 Thomas Petazzoni
2017-02-21 21:42 ` Peter Seiderer
2017-02-21 21:48 ` Thomas Petazzoni
2017-02-21 21:51 ` Romain Naour
2017-02-21 22:01 ` Peter Seiderer [this message]
2017-02-21 22:12 ` Thomas Petazzoni
2017-02-22 20:39 ` Peter Seiderer
2017-02-23 8:17 ` Thomas Petazzoni
2017-02-23 16:57 ` Peter Seiderer
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=20170221230119.5750f9cd@gmx.net \
--to=ps.report@gmx.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