Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-10-06
Date: Wed, 7 Oct 2015 09:07:49 -0300	[thread overview]
Message-ID: <56150B15.20402@zacarias.com.ar> (raw)
In-Reply-To: <561509B4.9000408@mind.be>

On 07/10/15 09:01, Arnout Vandecappelle wrote:

> On 07-10-15 11:19, Vicente Olivert Riera wrote:
>> Dear Thomas Petazzoni,
>>
>> On 10/07/2015 07:30 AM, Thomas Petazzoni wrote:
>>> Build statistics for 2015-10-06
>>> ===============================
>>
>>>      mips64el |                      pcre-8.37 | NOK | http://autobuild.buildroot.net/results/77f1c33d4315cce3f2d2387aa1368a63caac7468/
>>
>> I'm unable to reproduce this failure even using the same .config file.
>>
>> The failure looks like this:
>>
>> configure: error: You need a C++ compiler for C++ support.
>>
>> But the toolchain used in that config file does have a C++ compiler:
>>
>> $ file output/host/opt/ext-toolchain/bin/mips64el-ctng_n64-linux-gnu-g++
>> output/host/opt/ext-toolchain/bin/mips64el-ctng_n64-linux-gnu-g++: ELF
>> 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked
>> (uses shared libs), for GNU/Linux 2.6.18, stripped
>>
>> This was reported by your gcc75 autobuilder. Could you please have a look?
>
>   gcc75 => probably a bitflip?
>
>   Regards,
>   Arnout

Hi Arnout.
We already had one of those in gcc75:

http://buildroot-busybox.2317881.n4.nabble.com/PATCH-1-2-cmake-bump-to-version-3-3-2-td112954.html

Regards.

      reply	other threads:[~2015-10-07 12:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-07  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-10-06 Thomas Petazzoni
2015-10-07 10:19 ` Vicente Olivert Riera
2015-10-07 12:01   ` Arnout Vandecappelle
2015-10-07 12:07     ` Gustavo Zacarias [this message]

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=56150B15.20402@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