From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2012-06-20
Date: Thu, 21 Jun 2012 08:26:20 -0300 [thread overview]
Message-ID: <452b71440dc2b296d984b0765d2bdffc@zacarias.com.ar> (raw)
In-Reply-To: <20120621113207.616a649e@skate>
On 2012-06-21 06:32, Thomas Petazzoni wrote:
> Le Thu, 21 Jun 2012 10:49:07 +0200,
> Peter Korsgaard <jacmet@uclibc.org> a ?crit :
>> Thomas> Status : NOK
>> Thomas> Failure reason : ffmpeg-0.8.11
>> Thomas> Architecture : arm
>> Thomas> Submitted by : Thomas Petazzoni (Free Electrons build
>> server)
>> Thomas> Submitted at : 2012-06-20 20:57:51
>> Thomas> Git commit ID :
>> http://git.buildroot.net/buildroot/commit/?id=e9345f85822635291016f0b6e7cf855e07dbb028
>> Thomas> End of log :
>> http://autobuild.buildroot.net/results/3270ce7b816f7d141327a09e9c4273fd001827fb/build-end.log
>>
>> ARM/thumb mismatch?
>
> I don't know, maybe.
Not really, check back in the log, it's selecting ARMv6:
ARMv5TE enabled no
ARMv6 enabled yes
ARMv6T2 enabled yes
ARM VFP enabled yes
IWMMXT enabled no
NEON enabled no
My guess is that's it's doing build testing of the ISA and some
external toolchains default to something more than "generic".
So probably just make the logic more aggresive for ffmpeg's configure
parameters (just enable/disable instead of assuming it's disabled by
default which doesn't seem to be the case).
Regards.
next prev parent reply other threads:[~2012-06-21 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 6:31 [Buildroot] [autobuild.buildroot.net] Build results for 2012-06-20 Thomas Petazzoni
2012-06-21 8:49 ` Peter Korsgaard
2012-06-21 9:32 ` Thomas Petazzoni
2012-06-21 11:26 ` Gustavo Zacarias [this message]
2012-06-21 15:01 ` Peter Korsgaard
2012-06-21 20:32 ` Arnout Vandecappelle
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=452b71440dc2b296d984b0765d2bdffc@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