From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next 2/2] package/mariadb: bump version to 10.3.9
Date: Sat, 25 Aug 2018 23:26:48 +0200 [thread overview]
Message-ID: <o5u85fxpst.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20180825230514.1f0264dd@windsurf
Hi Thomas,
Am Sat, 25 Aug 2018 23:05:14 +0200 schrieb Thomas Petazzoni:
> We changed from -DWITH_SSL=bundled to -DWITH_SSL=OFF very recently, in
> commit 9276747defdd4f91ec21ba0930afdf6d947730b6. Do we really need SSL
> support in the host mariadb build ?
will test, thanks for the hint.
>> This bump also fixes broken atomic support for
>> BR2_TOOLCHAIN_HAS_LIBATOMIC=y with mariadb-10.2:
>>
>> [ 59%] Linking CXX executable mariabackup
>> ../../storage/innobase/libinnobase.a(handler0alter.cc.o): In function
>> `my_atomic_add64':
>> /home/bernd/buildroot/output/build/mariadb-10.2.17/include/my_atomic.h:
274:
>> undefined reference to `__sync_fetch_and_add_8'
>
> Is it the bump that fixes the atomic issue, or the fact that this patch
> adds the logic to link against libatomic when needed ?
Both ;)
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.
Regards, Bernd
next prev parent reply other threads:[~2018-08-25 21:26 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 [this message]
2018-08-25 21:39 ` Thomas Petazzoni
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=o5u85fxpst.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.de \
--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