From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/mono: disable boehm
Date: Thu, 21 Jan 2021 22:19:52 +0100 [thread overview]
Message-ID: <20210121221952.34051359@windsurf.home> (raw)
In-Reply-To: <20210120175443.157316-2-fontaine.fabrice@gmail.com>
On Wed, 20 Jan 2021 18:54:43 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> mono uses the Unity fork of recent Boehm since version 6.10.0.65 and
> https://github.com/mono/mono/commit/cc137237d86b0553e844dc34c9a3cbc5b20782c0
>
> However, this raises the following build failure:
>
> /tmp/instance-0/output-1/per-package/mono/host/arm-buildroot-linux-gnueabi/sysroot/usr/include/bits/string3.h:81: warning: memset used with constant zero length parameter; this could be due to transposed parameters
> ../../external/bdwgc/.libs/libgc.a(gc.o): In function `GC_steal_mark_stack':
> gc.c:(.text+0x1d18): undefined reference to `AO_store_full_emulation'
Well, isn't it simply forgetting to link with libatomic_ops ?
Look at your patch from 2018 on bdgwc:
http://lists.busybox.net/pipermail/buildroot/2018-November/235145.html,
the issue was the same, and was caused by the fact that it wasn't
linking with libatomic_ops.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-01-21 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 17:54 [Buildroot] [PATCH 1/2] package/mono: fix build with libunwind Fabrice Fontaine
2021-01-20 17:54 ` [Buildroot] [PATCH 2/2] package/mono: disable boehm Fabrice Fontaine
2021-01-21 21:19 ` Thomas Petazzoni [this message]
2021-01-21 21:14 ` [Buildroot] [PATCH 1/2] package/mono: fix build with libunwind Thomas Petazzoni
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=20210121221952.34051359@windsurf.home \
--to=thomas.petazzoni@bootlin.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.