All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/3] mariadb: bump version to 10.2.16
Date: Tue, 21 Aug 2018 17:35:56 +0200	[thread overview]
Message-ID: <20180821173556.7e6f7049@windsurf> (raw)
In-Reply-To: <d2ed2d47-33ae-1e39-5c66-b08d76913860@gmail.com>

Hello,

On Tue, 21 Aug 2018 06:59:51 -0700, Ryan Coe wrote:

> I have another patch ready.? I disabled building RocksDB to get rid of 
> the build error that was encountered.? Is that acceptable or should I 
> work on something else?? Thanks.

I have no idea what RocksDB is. Google tells me: "RocksDB is an
embeddable persistent key-value store for fast storage". Is this a new
optional dependency of MariaDB ? According to
https://mariadb.org/wp-content/uploads/2017/11/shenzhen2017-myrocks-in-mariadb.pdf
it seems to be new in 10.2.

So yes, this is a new thing, you can keep it disabled until someone
else is interested enough to enable/fix it.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-08-21 15:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26 16:37 [Buildroot] [PATCH v2 1/3] mariadb: move comments outside of define block Ryan Coe
2018-07-26 16:37 ` [Buildroot] [PATCH v2 2/3] mariadb: needs dynamic library support Ryan Coe
2018-07-29 13:20   ` Thomas Petazzoni
2018-08-23 20:18   ` Peter Korsgaard
2018-07-26 16:37 ` [Buildroot] [PATCH v2 3/3] mariadb: bump version to 10.2.16 Ryan Coe
2018-08-16 21:22   ` Thomas Petazzoni
2018-08-21 13:59     ` Ryan Coe
2018-08-21 15:35       ` Thomas Petazzoni [this message]
2018-07-29 13:19 ` [Buildroot] [PATCH v2 1/3] mariadb: move comments outside of define block Thomas Petazzoni
2018-08-23 20:15 ` Peter Korsgaard

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=20180821173556.7e6f7049@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 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.