From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2017-10-30
Date: Fri, 3 Nov 2017 15:28:54 +0100 [thread overview]
Message-ID: <20171103152854.4cfb8076@windsurf> (raw)
In-Reply-To: <CA+TH9VmEJrzwPHW8c6qR5K1bN5uTTce54vm9Fpq6met2we_bMA@mail.gmail.com>
Hello,
On Fri, 3 Nov 2017 15:18:24 +0100, Angelo Compagnucci wrote:
> > But you won't be able to reproduce the problem on your PC, because your
> > PC is x86-64, and the build failure seems to be specific to building on
> > ppc64le.
> >
> > Do you have an account on the gcc compile farm ?
>
> Of course no.
You could ask for one, see https://cfarm.tetaneutral.net/users/new/.
> I don't think I can help here. If the problem persists,
> probably the best way is to disable mono when the host is ppc64le.
Which host platforms does mono support? Should we enable it only for
x86/x86-64 build machines?
Do you think you could report this issue upstream?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-03 14:28 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2017-10-30 Thomas Petazzoni
2017-10-31 22:05 ` [Buildroot] Analysis of build " Thomas Petazzoni
2017-11-01 2:37 ` Matthew Weber
2017-11-01 9:45 ` Thomas Petazzoni
2017-11-01 10:01 ` Alexey Brodkin
2017-11-01 10:24 ` Thomas Petazzoni
2017-11-01 10:31 ` Alexey Brodkin
2017-11-02 2:31 ` Waldemar Brodkorb
2017-11-02 8:06 ` Thomas Petazzoni
2017-11-01 13:24 ` Matthew Weber
2017-11-01 13:37 ` Thomas Petazzoni
2017-11-01 10:17 ` Samuel Martin
2017-11-01 13:40 ` Thomas Petazzoni
2017-11-01 18:03 ` Baruch Siach
2017-11-02 10:54 ` Peter Korsgaard
2017-11-03 22:31 ` Peter Korsgaard
2017-11-02 10:46 ` Peter Korsgaard
2017-11-02 17:43 ` Yann E. MORIN
2017-11-02 18:08 ` Yann E. MORIN
2017-11-02 20:04 ` Thomas Petazzoni
2017-11-02 20:55 ` Yann E. MORIN
2017-11-02 22:21 ` Thomas Petazzoni
2017-11-02 22:30 ` Alexey Brodkin
2017-11-03 11:17 ` Angelo Compagnucci
2017-11-03 13:38 ` Thomas Petazzoni
2017-11-03 13:46 ` Angelo Compagnucci
2017-11-03 13:52 ` Thomas Petazzoni
2017-11-03 14:18 ` Angelo Compagnucci
2017-11-03 14:28 ` Thomas Petazzoni [this message]
2017-11-03 14:35 ` Angelo Compagnucci
2017-11-03 14:41 ` Thomas Petazzoni
2017-11-04 22:18 ` Arnout Vandecappelle
2017-11-04 22:20 ` Thomas Petazzoni
2017-11-04 22:36 ` Peter Korsgaard
2017-11-05 14:40 ` Thomas Petazzoni
2017-11-05 19:36 ` Peter Korsgaard
2017-11-05 22:35 ` Thomas Petazzoni
2017-11-09 20:58 ` Alexey Brodkin
2017-11-02 22:22 ` Alexey Brodkin
2017-11-08 12:49 ` Johan Oudinet
2017-11-08 16:16 ` Matthew Weber
2017-11-08 17:33 ` Yann E. MORIN
2017-11-08 19:35 ` Matthew Weber
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=20171103152854.4cfb8076@windsurf \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.