From: Jeff Layton <jlayton@primarydata.com>
To: chuck.lever@oracle.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH RFC 0/2] nfsdcltrack: don't use libsqlite3 functions that are too new
Date: Mon, 17 Nov 2014 13:32:13 -0500 [thread overview]
Message-ID: <1416249135-18736-1-git-send-email-jlayton@primarydata.com> (raw)
Chuck was having a problem building nfsdcltrack on a RHEL6 era box, due
to the fact that the libsqlite3 library there was too old. While we
could play games with autoconf, it's just easier to use older library
functions in these places so that we don't have to.
Jeff Layton (2):
nfsdcltrack: use sqlite3_close instead of sqlite3_close_v2
nfsdcltrack: use sqlite3_errmsg instead of sqlite3_errstr
utils/nfsdcltrack/sqlite.c | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
--
2.1.0
next reply other threads:[~2014-11-17 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 18:32 Jeff Layton [this message]
2014-11-17 18:32 ` [PATCH RFC 1/2] nfsdcltrack: use sqlite3_close instead of sqlite3_close_v2 Jeff Layton
2014-11-17 18:32 ` [PATCH RFC 2/2] nfsdcltrack: use sqlite3_errmsg instead of sqlite3_errstr Jeff Layton
2014-11-17 19:04 ` [PATCH RFC 0/2] nfsdcltrack: don't use libsqlite3 functions that are too new Steve Dickson
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=1416249135-18736-1-git-send-email-jlayton@primarydata.com \
--to=jlayton@primarydata.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.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