All of lore.kernel.org
 help / color / mirror / Atom feed
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 14:52:57 +0100	[thread overview]
Message-ID: <20171103145257.172edd86@windsurf> (raw)
In-Reply-To: <CA+TH9V=Uw2C7L4M0P9+uos5M66EGjLLHFFq50EqJPEGppKhV2Q@mail.gmail.com>

Hello,

On Fri, 3 Nov 2017 14:46:15 +0100, Angelo Compagnucci wrote:

> > Unhandled Exception:
> > System.ExecutionEngineException: System.IndexOutOfRangeException: Index was outside the bounds of the array. ---> System.IndexOutOfRangeException: Index was outside the bounds of the array.
> >    --- End of inner exception stack trace ---
> > [...]  
> 
> This is really strange. This error means that the code inside a mono
> vm running program is failing, so mono is running correctly!
> 
> >
> > So it seems like host-mono doesn't build on a ppc64le machine. Looking
> > at the host-monolite tarball, I see it's a bunch of .dll built for x86.
> > Is this supposed to work on other architectures as well?  
> 
> Yes it is. host-mono it's used to bootstrap the mono compilation for
> the target so it must run on the host architecture.

I don't follow you here.

gcc112 is a ppc64le machine, and I'm cross-compiling for ARM.

Is it possible for those x86 .dll provided by monolite to be used on a
ppc64le machine ?

> IMHO seems like something related to memory, mono changed so much in
> the latests releases and it uses much more memory during the
> compilation. I cannot reproduce the bug on my setup with 16GB of RAM
> and the config that fails on the autobuilder.

The ppc64le machine that causes the failure has 256GB of RAM.

> Could you give me the config you are using?

It's just:

BR2_arm=y
BR2_PACKAGE_MONO=y

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 ?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-11-03 13:52 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 [this message]
2017-11-03 14:18             ` Angelo Compagnucci
2017-11-03 14:28               ` Thomas Petazzoni
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=20171103145257.172edd86@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.