Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2015-11-18
Date: Sat, 21 Nov 2015 23:17:26 +0100	[thread overview]
Message-ID: <5650ED76.6070409@mind.be> (raw)
In-Reply-To: <CAFGQKxd7LUYDN-whwsdhenu=bMJXnd7nQ=ungrxvt2NnMG5fiA@mail.gmail.com>

On 21-11-15 15:45, Martin Bark wrote:
> Thomas, All,
> 
> On 19 November 2015 at 23:15, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>> Hello,
>>
>> J?r?me, Johan, Bernd, Yann, Martin, Gustavo, R?mi, Samuel, Alexey,
>> Waldemar, Clayton, please read below, there are some interesting issues
>> for you :-) Thanks !
>>
>> On Thu, 19 Nov 2015 08:30:13 +0100 (CET), Thomas Petazzoni wrote:

[snip]

>>>       x86_64 |              host-nodejs-4.1.2 | NOK | http://autobuild.buildroot.net/results/3fd1d18f0535bb8b969f808a5837c4a8111e69b9/
>>
>> Seems like nodejs doesn't like the native gcc 4.7 that this machine
>> uses. Martin, can you have a look ?
>>
>> BTW Martin, there's also this other error that popped up on a different
>> machine:
>> http://autobuild.buildroot.org/results/72b/72b80a434547931e1deb6f0ba793a6d68accc9a2/build-end.log.
> 
> Yes i think you're right, the issue looks like gcc 4.7 on the host.
> This issue https://github.com/nodejs/node-gyp/issues/790 and this one
> https://github.com/nodejs/node/issues/432 have similar build issues
> and they both come down to node.js needs at least gcc 4.8
> 
> The Config.in already has BR2_TOOLCHAIN_GCC_AT_LEAST_4_8 for node.js
> 4.x, is there a way to specify this for the host build too?

 There currently isn't.

 I will try to make a patch that adds BR2_HOST_GCC_AT_LEAST_*, but I don't have
the older gcc to test it with. There are three packages that have
BR2_TOOLCHAIN_GCC_AT_LEAST and that also have a host variant:

- nodejs (4.8)
- directfb (4.5), but host-directfb is not used and never has been used
- cmake (4.7), but that's only needed for ctest which needs jsoncpp which
doesn't have a host variant.

 So probably only nodejs will need this, but it would be good to test host-cmake
with gcc 4.6 or earlier. Does anyone have that lying around?

 Regards,
 Arnout

[snip]


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2015-11-21 22:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-19  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-11-18 Thomas Petazzoni
2015-11-19 23:15 ` [Buildroot] Analysis of build " Thomas Petazzoni
2015-11-20  0:17   ` Ryan Barnett
2015-11-20 15:29   ` Gustavo Zacarias
2015-11-20 15:45     ` Thomas Petazzoni
2015-11-22  7:53     ` Waldemar Brodkorb
2015-11-20 21:01   ` Alexey Brodkin
2015-11-24 12:10     ` Alexey Brodkin
2015-11-20 22:26   ` Arnout Vandecappelle
2015-11-21  8:23     ` Thomas Petazzoni
2015-11-21 21:14       ` Arnout Vandecappelle
2015-11-21 14:45   ` Martin Bark
2015-11-21 22:17     ` Arnout Vandecappelle [this message]
2015-11-22 18:31       ` Martin Bark
2015-11-23  6:22   ` Rodrigo Rebello

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=5650ED76.6070409@mind.be \
    --to=arnout@mind.be \
    --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