I've been writing some extensions with great success however, I have
one that I'm working on (rewriting an existing extension that has never
functioned properly to the best of my knowledge) that is causing me
headaches.
This problem seems to occur regardless of the version of PHP being
utilized.
By using a simple and basic config.m4 file that substantiates the
required files, building PHP with the module as a shared extension
complains with the following error message in the log:
[Sun Mar 6 17:03:09 2005] [error] PHP Warning: rrdtool: Unable to
register functions, unable to load in Unknown on line 0
however, the module functions appears to work properly.
If I build the extension embedded into PHP, I still get the same
message in the log however the modules functions don't work properly
(doesn't work as intended) and for those who say they don't understand
what "doesn't works properly" or "work as intended" and are looking for
more clarity, all I can say is this, it does not do what it is supposed
to do and if you need more clarity than that you will have to examine
the source code and the environment and provide me with a better answer
because I can't explain it other than "it doesn't do what it's supposed
to do" for the lack of better words.
Now, by utilizing a very elaborate and complex config.m4 file and
building in either manor I still receive this error message in the log
but the module still functions properly as a shared extension but
refuses to function properly when it is embedded into PHP.
I've been seeking assistance with the problem for several weeks now and
while I have received some responses, I have made little progress in
solving this matter or gaining a better insight to the cause/solution
to this problem.
I would like to note that making it a shared extension and not loading
it via a php.ini entry, it does not display the error message in the
log but the module functions work properly.
I've examined the source carefully as well as a couple of other people
and nothing appears to be outside the normal extension API, I can only
verify that this problem occurs with this particular module under Mac
OSX 10.2.x - 10.3.x and any version of PHP from 4.3.4 and newer (never
tested on earlier versions than 4.3.4).
If you want to duplicate the problem it's simple and easy, I can send
you the source, you will require access to a Macintosh computer (which
I can provide since I have 14 of them) with OSXS 10.3.x installed that
are accessible and all you have to do is add is build it.
While there is nothing outside of normal programming occurring and the
API seems to be adhered to, I cannot for the life of me figure out what
is going on and can only assume that the problem is a bug in the API
being the culprit.
Anyone willing to take a stab at it?
-- Dale
