From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 141] New: New php package option: build with external/interal sqlite3 support (for pdo_sqlite)
Date: Tue, 3 Mar 2009 17:54:42 +0000 (UTC) [thread overview]
Message-ID: <bug-141-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=141
Host: i686-linux
Target: arm-softfloat-linux-uclibcgnueabi
Summary: New php package option: build with external/interal
sqlite3 support (for pdo_sqlite)
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: gustavo at zacarias.com.ar
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created an attachment (id=97)
--> (https://bugs.busybox.net/attachment.cgi?id=97)
Allow php to use external sqlite3 for pdo_sqlite
This patch add a new option to allow PHP to be built against an external
sqlite3 library instead of the bundled one.
PHP 5.2.9 bundles sqlite-3.3.7, latest is 3.6.11 which adds functionality.
Also it might be troublesome to build/work with a db from CLI 3.6.11 and then
try to use that with PHP's bundled older version.
Tested against 3.6.11 from bug #139 though it should work with current svn
3.6.10 also.
BTW you can close bug #137 since it's done.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2009-03-03 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 17:54 bugzilla at busybox.net [this message]
2009-03-04 21:01 ` [Buildroot] [Bug 141] New php package option: build with external/interal sqlite3 support (for pdo_sqlite) bugzilla at busybox.net
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=bug-141-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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.