Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:21816
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <43EA8EBC.3040902@lerdorf.com>
Date: Wed, 08 Feb 2006 16:37:16 -0800
User-Agent: Thunderbird 1.5 (Macintosh/20051201)
MIME-Version: 1.0
To: Andrew Mather <an.dromeda@btconnect.com>
CC: internals@lists.php.net
References: <000e01c62cfd$ef7443c0$ca5f8a51@VaioCen>
In-Reply-To: <000e01c62cfd$ef7443c0$ca5f8a51@VaioCen>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Writing PHP extensions without re-building PHP
From: rasmus@lerdorf.com (Rasmus Lerdorf)

Andrew Mather wrote:
> ps: the example given at http://www.zend.com/php/internals/ makes sense, as such,
> but while the first two command (phpize, ./configure, seem to work, the make command
> throws errors like confetti, based on the lack of php.h, zend.h etc in an environment that
> was installed 'out of the box' of Suse 9.3, rather than to the bespoke 'we can rebuild it'
> requirements of the example. 
> 
> Making such an example compile and run as a dynamically loadable module in the
> described environment would be my goal, allowing me to extend it as required later.

Perhaps you didn't install the -dev package in SUSE?  I know nothing 
about SUSE and how they chose to package PHP, but if you installed PHP 
from our sources, it would have installed those files.  I am sure SUSE 
has those hidden away somewhere.

-Rasmus