From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 2/2] package/mariadb: bump version to 10.3.9
Date: Sat, 25 Aug 2018 23:39:58 +0200 [thread overview]
Message-ID: <20180825233958.29369922@windsurf> (raw)
In-Reply-To: <o5u85fxpst.ln2@ID-313208.user.individual.net>
Hello,
On Sat, 25 Aug 2018 23:26:48 +0200, Bernd Kuhls wrote:
> In unpatched next branch the build on arc fails with
> "error atomic ops for this platform are not implemented", no cxxflags nor
> CONF_OPTS will solve that.
>
> Only when bumping to 10.3 you get past this build error just to see the
> "undefined reference to `__sync_fetch_and_add_8'" error later on.
> To solve this the changes in this patch are needed.
So it still needs some atomic intrinsics, so the package should:
depends on BR2_TOOLCHAIN_HAS_ATOMIC || BR2_TOOLCHAIN_HAS_SYNC_4
Indeed, atomic intrinsics are not always available, even when you link
with -latomic: gcc versions before gcc 4.8 did not have libatomic.
Build a SPARC gcc 4.7 toolchain, and try to build this package, you'll
be surprised :-)
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-25 21:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-25 20:44 [Buildroot] [PATCH/next/RFC 1/2] package/mariadb: handle missing ucontext_t Bernd Kuhls
2018-08-25 20:44 ` [Buildroot] [PATCH/next 2/2] package/mariadb: bump version to 10.3.9 Bernd Kuhls
2018-08-25 21:05 ` Thomas Petazzoni
2018-08-25 21:26 ` Bernd Kuhls
2018-08-25 21:39 ` Thomas Petazzoni [this message]
2018-08-25 21:54 ` Bernd Kuhls
2018-08-25 22:01 ` Thomas Petazzoni
2018-08-26 11:48 ` Bernd Kuhls
2018-08-27 9:04 ` 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=20180825233958.29369922@windsurf \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox