I'm attempting to build some PECL modules on fully updated CentOS 4.2
system. Preferably pack them into nice RPM packages. However, seems
I'm missing something. For example, this is what I get for sqlite module:
$ pear makerpm SQLite-1.0.3.tgz
`phpize' failed
The php-devel package is installed (so I do have phpize command). It's
just that it is failing. If I unpack the files into directory, and do
"pear build" or "pear install", I'm getting a bit more
verbose error:
$ pear build
running: phpize
configure.in:9: warning: underquoted definition of PHP_WITH_PHP_CONFIG
run info '(automake)Extending aclocal'
or see http://sources.redhat.com/automake/automake.html#Extending-aclocal
configure.in:32: warning: underquoted definition of PHP_EXT_BUILDDIR
configure.in:33: warning: underquoted definition of PHP_EXT_DIR
configure.in:34: warning: underquoted definition of PHP_EXT_SRCDIR
configure.in:35: warning: underquoted definition of PHP_ALWAYS_SHARED
acinclude.m4:19: warning: underquoted definition of PHP_PROG_RE2C
configure.in:65: error: possibly undefined macro: AC_PROG_LIBTOOL
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
`phpize' failed
I do remember being able to build and install couple of PECL modules
some time ago on different CentOS 4.2 system. Howerver, I'm failing to
see why the builds are now failing. The two systems look more or less
the same (except hardware, the old one was i686, the new one is i586).
I'm not an automake/autoconf expert, the above message looks to me more
or less like names of Spanish vilages (in other words, I'm completely
culeless here).
While on the topic of PECL/PEAR, packaging PEAR modules into RPMs kinda
works. The "pear makerpm" produces unusable spec files most of the
time, but with a bit of editing of those spec files, I got my RPMs.
Mostly documentation, "ugly" package names, and by default files get
installed outside of PHP/Pear search path (easy to fix manually in spec
file). Known bug in pear or am I doing something awfully wrong?
Anyhow, any help would be geately appriciated.
On 12/28/05, Aleksandar Milivojevic <alex at milivojevic.org> wrote:> I'm attempting to build some PECL modules on fully updated CentOS 4.2 > system. Preferably pack them into nice RPM packages. However, seems > I'm missing something. For example, this is what I get for sqlite module: > > $ pear makerpm SQLite-1.0.3.tgz > `phpize' failed > > The php-devel package is installed (so I do have phpize command). It's > just that it is failing. If I unpack the files into directory, and do > "pear build" or "pear install", I'm getting a bit more verbose error: > > $ pear build > running: phpize > configure.in:9: warning: underquoted definition of PHP_WITH_PHP_CONFIG > run info '(automake)Extending aclocal' > or see http://sources.redhat.com/automake/automake.html#Extending-aclocal > configure.in:32: warning: underquoted definition of PHP_EXT_BUILDDIR > configure.in:33: warning: underquoted definition of PHP_EXT_DIR > configure.in:34: warning: underquoted definition of PHP_EXT_SRCDIR > configure.in:35: warning: underquoted definition of PHP_ALWAYS_SHARED > acinclude.m4:19: warning: underquoted definition of PHP_PROG_RE2C > configure.in:65: error: possibly undefined macro: AC_PROG_LIBTOOL > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. > `phpize' failed > > I do remember being able to build and install couple of PECL modules > some time ago on different CentOS 4.2 system. Howerver, I'm failing to > see why the builds are now failing. The two systems look more or less > the same (except hardware, the old one was i686, the new one is i586). > I'm not an automake/autoconf expert, the above message looks to me more > or less like names of Spanish vilages (in other words, I'm completely > culeless here). > > While on the topic of PECL/PEAR, packaging PEAR modules into RPMs kinda > works. The "pear makerpm" produces unusable spec files most of the > time, but with a bit of editing of those spec files, I got my RPMs. > Mostly documentation, "ugly" package names, and by default files get > installed outside of PHP/Pear search path (easy to fix manually in spec > file). Known bug in pear or am I doing something awfully wrong? > > Anyhow, any help would be geately appriciated.The packaging of addition php-pear modules is currently being discussed, but has some issues with it. In the mean time some, if not all of the php modules you want are available via yum from dag.wieers.com/packages and centos.karan.org. While not official centos packages, both packagers are very active in centos development and are quite good. -- Jim Perrin System Architect - UIT Ft Gordon & US Army Signal Center
On Wed, 2005-12-28 at 21:40 -0600, Aleksandar Milivojevic wrote:> I'm attempting to build some PECL modules on fully updated CentOS 4.2 > system. Preferably pack them into nice RPM packages. However, seems > I'm missing something. For example, this is what I get for sqlite module: > > $ pear makerpm SQLite-1.0.3.tgz > `phpize' failed > > The php-devel package is installed (so I do have phpize command). It's > just that it is failing. If I unpack the files into directory, and do > "pear build" or "pear install", I'm getting a bit more verbose error: > > $ pear build > running: phpize > configure.in:9: warning: underquoted definition of PHP_WITH_PHP_CONFIG > run info '(automake)Extending aclocal' > or see http://sources.redhat.com/automake/automake.html#Extending-aclocal > configure.in:32: warning: underquoted definition of PHP_EXT_BUILDDIR > configure.in:33: warning: underquoted definition of PHP_EXT_DIR > configure.in:34: warning: underquoted definition of PHP_EXT_SRCDIR > configure.in:35: warning: underquoted definition of PHP_ALWAYS_SHARED > acinclude.m4:19: warning: underquoted definition of PHP_PROG_RE2C > configure.in:65: error: possibly undefined macro: AC_PROG_LIBTOOL > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. > `phpize' failed > > I do remember being able to build and install couple of PECL modules > some time ago on different CentOS 4.2 system. Howerver, I'm failing to > see why the builds are now failing. The two systems look more or less > the same (except hardware, the old one was i686, the new one is i586). > I'm not an automake/autoconf expert, the above message looks to me more > or less like names of Spanish vilages (in other words, I'm completely > culeless here). > > While on the topic of PECL/PEAR, packaging PEAR modules into RPMs kinda > works. The "pear makerpm" produces unusable spec files most of the > time, but with a bit of editing of those spec files, I got my RPMs. > Mostly documentation, "ugly" package names, and by default files get > installed outside of PHP/Pear search path (easy to fix manually in spec > file). Known bug in pear or am I doing something awfully wrong?---- somewhat of a hack but check out... http://wiki.horde.org/MimeMagic?referrer=HowTo Craig
-----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Aleksandar Milivojevic Sent: Thursday, December 29, 2005 6:51 AM To: CentOS mailing list Subject: Re: [CentOS] Building PHP PECL modules Jim Perrin wrote:> The packaging of addition php-pear modules is currently being > discussed, but has some issues with it. In the mean time some, if not > all of the php modules you want are available via yum from > dag.wieers.com/packages and centos.karan.org. While not official > centos packages, both packagers are very active in centos development > and are quite good.I know about those, but as usual, I need some more stuff ;-) Anyhow, would be nice to know how Dag and Karanbir managed to compile PECL modules. -------------------------------------------------------- As far as the SQLite package, I just ran into this and evidently SQLite is enabled by default in php, however the centos rpm is explicity set to turn off SQLite support. So, I just snagged the source rpm, edited the SPEC file to remove the --without-sqlite and voila, my custom rpm with SQLite installed. Hope that's helpful.
-----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Matt Hyclak Sent: Thursday, December 29, 2005 9:10 AM To: CentOS ML Subject: Re: [CentOS] Building PHP PECL modules On Thu, Dec 29, 2005 at 09:05:23AM -0600, Johnny Hughes enlightened us:> > On Thu, Dec 29, 2005 at 08:36:35AM -0600, Bassett, Mark enlightenedus:> > > As far as the SQLite package, I just ran into this and evidentlySQLite> > > is enabled by default in php, however the centos rpm is explicityset to> > > turn off SQLite support. So, I just snagged the source rpm,edited the> > > SPEC file to remove the --without-sqlite and voila, my custom rpmwith> > > SQLite installed. > > > > > > Hope that's helpful. > > > > > > > I'm guessing that comes from upstream, since they don't distributeSQLite.> > Perhaps a RFE for the CentOS php rpm to enable that would be inorder if> > enough folks think it should be included since CentOS *does*distribute> > SQLite. > > We distribute SQLite only for yum ... and that doesn't require SQLite > PHP support :) > > We won't (I don't think) compile the PHP4 with SQLite support, so asto> maintain compatibility with upstream ... though I don't have a problem > with SQLite being in the php5 that is in CentOSPlusThat's the one I rebuilt anyway ;) We are a major php shop so we run php5 across the board. I'm all for including that in centosplus. If I remember correctly they also do a --disable-dom but then add it in later with a php-dom rpm package, so I'm not really sure what that one's all about.
Am Do, den 29.12.2005 schrieb Aleksandar Milivojevic um 4:40:> I'm attempting to build some PECL modules on fully updated CentOS 4.2 > system. Preferably pack them into nice RPM packages. However, seems > I'm missing something. For example, this is what I get for sqlite module: > > $ pear makerpm SQLite-1.0.3.tgz > `phpize' failed > > The php-devel package is installed (so I do have phpize command). It's > just that it is failing. If I unpack the files into directory, and do > "pear build" or "pear install", I'm getting a bit more verbose error:Hi Aleksandar :) I would guess you know http://phprpms.sourceforge.net/sqlite But maybe not. For other PECL modules (I recently made a fileinfo RPM for horde/imp) following .spec might be a help: $ cat /home/rpmbuild/SPECS/php-pecl-fileinfo.spec %define php_extdir %(php-config --extension-dir || echo %{_libdir}/php4) Summary: PEAR: libmagic bindings Name: php-pecl-fileinfo Version: 1.0.1 Release: 1.ad License: PHP Group: Development/Libraries Source: http://pecl.php.net/get/Fileinfo-%{version}.tgz URL: http://pecl.php.net/ BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n) BuildRequires: php-devel, php, autoconf, automake, libtool, gcc-c++ Requires: php %description This extension allows retrieval of information regarding vast majority of file. This information may include dimensions, quality, length etc... Additionally it can also be used to retrieve the mime type for a particular file and for text files proper language encoding. %prep %setup -n Fileinfo-%{version} %build phpize %configure make %install rm -rf %{buildroot} make install INSTALL_ROOT=%{buildroot} # Drop in the bit of configuration mkdir -p %{buildroot}%{_sysconfdir}/php.d cat > %{buildroot}%{_sysconfdir}/php.d/fileinfo.ini << 'EOF' ; Enable Fileinfo extension module extension=fileinfo.so EOF %clean rm -rf %{buildroot} %files %defattr(-, root, root, 0755) %doc CREDITS EXPERIMENTAL %config(noreplace) %{_sysconfdir}/php.d/fileinfo.ini %{php_extdir}/fileinfo.so %changelog * Wed Dec 07 2005 Alexander Dalloz <me at camouflage> - Initial build on CentOS 4.2 Alexander -- Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773 legal statement: http://www.uni-x.org/legal.html Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.35_FC2smp Serendipity 18:53:26 up 24 days, 23:30, load average: 0.18, 0.18, 0.18 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Dies ist ein digital signierter Nachrichtenteil URL: <http://lists.centos.org/pipermail/centos/attachments/20051229/db2f149c/attachment-0001.sig>
Quoting Alexander Dalloz <ad+lists at uni-x.org>:> For other PECL modules (I recently made a fileinfo RPM for horde/imp) > following .spec might be a help: > > $ cat /home/rpmbuild/SPECS/php-pecl-fileinfo.specHi Alexander ;-) Thanks for that spec file. It surelly will be heavilly used :-) Anyhow, one thing I just noticed is that I'm acutally unable to build PECL stuff only on this single one machine. I can't find any real difference in set of installed RPMs on this machine and all others. The only difference between it and other machines is that this one is i586. But again, that shouldn't trigger the kind of error that I'm getting. Hm, strange. Very strange... ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
Aleksandar Milivojevic wrote:> I'm attempting to build some PECL modules on fully updated CentOS 4.2 > system. Preferably pack them into nice RPM packages. However, seems > I'm missing something. For example, this is what I get for sqlite module: > > $ pear makerpm SQLite-1.0.3.tgz > `phpize' failed > > The php-devel package is installed (so I do have phpize command). It's > just that it is failing. If I unpack the files into directory, and do > "pear build" or "pear install", I'm getting a bit more verbose error: > > $ pear build > running: phpize > configure.in:9: warning: underquoted definition of PHP_WITH_PHP_CONFIG > run info '(automake)Extending aclocal' > or see http://sources.redhat.com/automake/automake.html#Extending-aclocal > configure.in:32: warning: underquoted definition of PHP_EXT_BUILDDIR > configure.in:33: warning: underquoted definition of PHP_EXT_DIR > configure.in:34: warning: underquoted definition of PHP_EXT_SRCDIR > configure.in:35: warning: underquoted definition of PHP_ALWAYS_SHARED > acinclude.m4:19: warning: underquoted definition of PHP_PROG_RE2C > configure.in:65: error: possibly undefined macro: AC_PROG_LIBTOOL > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. > `phpize' failedAh... Where were my eyes. Probably joined my brain that went on vacation long time ago... The error message complains about undefined macro "AC_PROG_LIBTOOL". Of course. I was missing the libtool utility. "yum install libtool", and now PECL modules are happily building. Thanks to everyone who tried to help me out. There were some interesting bits of information in replies. Especially thanks to Alexnader for the spec file. Happy New Year to everyone.