From: Phil Blundell <philb@gnu.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] sqlite3: enable USE_PREAD
Date: Sat, 22 Sep 2012 17:50:21 +0100 [thread overview]
Message-ID: <1348332621.4444.219.camel@x121e.pbcl.net> (raw)
This gives a small but measureable performance improvement for
I/O heavy workloads.
Signed-off-by: Phil Blundell <pb@pbcl.net>
---
meta/recipes-support/sqlite/sqlite3.inc | 4 ++++
meta/recipes-support/sqlite/sqlite3_3.7.13.bb | 2 +-
2 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/meta/recipes-support/sqlite/sqlite3.inc b/meta/recipes-support/sqlite/sqlite3.inc
index 0cc5d65..70841f8 100644
--- a/meta/recipes-support/sqlite/sqlite3.inc
+++ b/meta/recipes-support/sqlite/sqlite3.inc
@@ -17,6 +17,10 @@ export config_TARGET_LINK = "${CCLD}"
export config_TARGET_CFLAGS = "${CFLAGS}"
export config_TARGET_LFLAGS = "${LDFLAGS}"
+# pread() is in POSIX.1-2001 so any reasonable system must surely support it
+BUILD_CFLAGS += "-DUSE_PREAD"
+TARGET_CFLAGS += "-DUSE_PREAD"
+
PACKAGES = "lib${BPN} lib${BPN}-dev lib${BPN}-doc ${PN}-dbg lib${BPN}-staticdev ${PN}"
FILES_${PN} = "${bindir}/*"
diff --git a/meta/recipes-support/sqlite/sqlite3_3.7.13.bb b/meta/recipes-support/sqlite/sqlite3_3.7.13.bb
index 4e050a3..48b50ac 100644
--- a/meta/recipes-support/sqlite/sqlite3_3.7.13.bb
+++ b/meta/recipes-support/sqlite/sqlite3_3.7.13.bb
@@ -2,7 +2,7 @@ require sqlite3.inc
LIC_FILES_CHKSUM = "file://sqlite3.h;endline=11;md5=65f0a57ca6928710b418c094b3570bb0"
-PR = "r0"
+PR = "r1"
SRC_URI = "http://www.sqlite.org/sqlite-autoconf-3071300.tar.gz"
S = "${WORKDIR}/sqlite-autoconf-3071300"
--
1.7.9
next reply other threads:[~2012-09-22 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 16:50 Phil Blundell [this message]
2012-09-24 10:20 ` [PATCH] sqlite3: enable USE_PREAD Richard Purdie
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=1348332621.4444.219.camel@x121e.pbcl.net \
--to=philb@gnu.org \
--cc=openembedded-core@lists.openembedded.org \
/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