From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/mono: Disabling for sparc32
Date: Sun, 24 Apr 2016 19:54:35 +0200 [thread overview]
Message-ID: <20160424175435.GX26720@waldemar-brodkorb.de> (raw)
In-Reply-To: <CA+TH9V=-d3k7U11mpfz=EVuNHFAJZRqwqzNRZppMSNrEF=xvnw@mail.gmail.com>
Hi Angelo,
Angelo Compagnucci wrote,
> Dear Thomas Petazzoni,
>
> 2016-04-24 17:23 GMT+02:00 Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com>:
> > Hello,
> >
> > On Sun, 24 Apr 2016 16:16:27 +0200, Angelo Compagnucci wrote:
> >> Mono cannot be compiled for sparc32 (v8/leon) so disabling it.
> >>
> >> Signed-off-by: Angelo Compagnucci <angelo.compagnucci@gmail.com>
> >> ---
> >> package/mono/Config.in | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> >> default y if (BR2_arm || BR2_armeb || BR2_i386 || BR2_mips || \
> >> - BR2_mipsel || BR2_powerpc || BR2_sparc || BR2_x86_64)
> >> + BR2_mipsel || BR2_powerpc || BR2_sparc64 || BR2_x86_64)
> >
> > And you're enabling for sparc64 at the same time, which is not
> > explained in your commit log.
>
> Mmm, right.
>
> >
> > Also, Waldemar sent a patch one hour before that disables it for SPARC,
> > without enabling it for SPARC64, because it also doesn't build for
> > SPARC64.
>
> The problem is this one:
>
> "cannot find crti.o: No such file or directory"
>
> Suggesting me the problem is located more in the toolchain than in
> mono for sparc64, but I have no clue on this.
I had other issues regarding ucontext.h struct mismatches.
best regards
Waldemar
prev parent reply other threads:[~2016-04-24 17:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-24 14:16 [Buildroot] [PATCH] package/mono: Disabling for sparc32 Angelo Compagnucci
2016-04-24 15:23 ` Thomas Petazzoni
2016-04-24 17:42 ` Angelo Compagnucci
2016-04-24 17:54 ` Waldemar Brodkorb [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=20160424175435.GX26720@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--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