Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: jacmet at uclibc.org <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/php
Date: Sat, 21 Feb 2009 09:06:44 +0000 (UTC)	[thread overview]
Message-ID: <20090221090644.DBFBC76564@busybox.osuosl.org> (raw)

Author: jacmet
Date: 2009-02-21 09:06:43 +0000 (Sat, 21 Feb 2009)
New Revision: 25405

Log:
php: fix sqlite module

- php comes with it's own embedded sqlite, so no need to select sqlite
- disable largefile support for !BR2_LARGEFILE
- php somehow forgets to link with -ldl, breaking the sqlite extension.
  Fix it by disabling the (unused?) modload support in sqlite.

Modified:
   trunk/buildroot/package/php/Config.ext
   trunk/buildroot/package/php/php.mk


Changeset:
Modified: trunk/buildroot/package/php/Config.ext
===================================================================
--- trunk/buildroot/package/php/Config.ext	2009-02-20 21:55:32 UTC (rev 25404)
+++ trunk/buildroot/package/php/Config.ext	2009-02-21 09:06:43 UTC (rev 25405)
@@ -131,7 +131,6 @@
 config BR2_PACKAGE_PHP_EXT_SQLITE
 	bool "sqlite"
 	depends on BR2_PACKAGE_PHP
-	select BR2_PACKAGE_SQLITE
 	default y
 	help
 	  SQLite

Modified: trunk/buildroot/package/php/php.mk
===================================================================
--- trunk/buildroot/package/php/php.mk	2009-02-20 21:55:32 UTC (rev 25404)
+++ trunk/buildroot/package/php/php.mk	2009-02-21 09:06:43 UTC (rev 25405)
@@ -109,7 +109,9 @@
 ### Database extensions
 ifeq ($(BR2_PACKAGE_PHP_EXT_SQLITE),y)
 	PHP_CONFIGURE+=--with-sqlite
-	PHP_DEPS+=sqlite
+ifneq ($(BR2_LARGEFILE),y)
+	PHP_CFLAGS+= -DSQLITE_DISABLE_LFS
+endif
 ifeq ($(BR2_PACKAGE_PHP_EXT_SQLITE_UTF8),y)
 	PHP_CONFIGURE+=--enable-sqlite-utf8
 endif
@@ -118,6 +120,7 @@
 	PHP_CONFIGURE+=--enable-pdo
 ifeq ($(BR2_PACKAGE_PHP_EXT_PDO_SQLITE),y)
 	PHP_CONFIGURE+=--with-pdo-sqlite
+	PHP_CFLAGS+= -DSQLITE_OMIT_LOAD_EXTENSION
 endif
 ifeq ($(BR2_PACKAGE_PHP_EXT_PDO_MYSQL),y)
 	PHP_CONFIGURE+=--with-pdo-mysql=$(STAGING_DIR)/usr
@@ -164,7 +167,7 @@
 	touch $@
 
 $(PHP_DIR)/.built: $(PHP_DIR)/.configured
-	$(MAKE) CC=$(TARGET_CC) -C $(PHP_DIR)
+	$(MAKE) CC="$(TARGET_CC) $(PHP_CFLAGS)" -C $(PHP_DIR)
 	touch $@
 
 $(PHP_DIR)/.staged: $(PHP_DIR)/.built

             reply	other threads:[~2009-02-21  9:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-21  9:06 jacmet at uclibc.org [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-03-04 20:58 [Buildroot] svn commit: trunk/buildroot/package/php jacmet at uclibc.org
2009-03-04 20:58 jacmet at uclibc.org
2009-03-02 19:05 jacmet at uclibc.org
2009-02-25 19:51 jacmet at uclibc.org
2009-02-21  9:06 jacmet at uclibc.org
2009-02-20 21:55 jacmet at uclibc.org
2009-02-20 15:13 jacmet at uclibc.org
2009-01-25 20:59 ulf at uclibc.org
2009-01-11 20:08 ulf at uclibc.org
2008-12-13 11:01 tpetazzoni at uclibc.org
2008-06-16  9:49 jacmet at uclibc.org
2008-06-01 19:42 antab at uclibc.org
2008-06-01 18:04 antab at uclibc.org
2008-06-01 19:31 ` Peter Korsgaard
2008-06-02 12:11 ` Peter Korsgaard
2008-06-02 13:15   ` Gustavo Zacarias
2008-03-25  8:49 jacmet at uclibc.org
2008-03-11 18:14 ninevoltz at uclibc.org
2008-03-06 18:21 ninevoltz at uclibc.org
2007-08-19 21:02 ulf at uclibc.org

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=20090221090644.DBFBC76564@busybox.osuosl.org \
    --to=jacmet@uclibc.org \
    --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