ID: 35292
User updated by: dgrimes at scvl dot com
Reported By: dgrimes at scvl dot com
-Status: Bogus
+Status: Open
Bug Type: MySQL related
Operating System: SCO OpenServer
PHP Version: 4.4.1
New Comment:
I've done some more research. I took the ext/mysql/php_mysql.c and
ext/mysql/php_mysql.h files from version 4.2.3 and copied them into the
4.4.1 tree. Recompiled and installed. The problem has gone away. So,
somewhere therein lies the trouble. I'll continue to pursue the cause
and if I figure it out I'll let you know what I find. The one question
I have is, if I have questions regarding specific functions or
variables, can I get answers to those questions?
Thanks,
Dean
Previous Comments:
------------------------------------------------------------------------
[2005-11-21 15:06:46] dgrimes at scvl dot com
Wow. I truly didn't expect that response; especially from an
organization as highly respected as is PHP. Obviously I have offended
you in some way and for that I apologize. Should I take your response
to mean that in the future any problems I encounter between PHP and
OpenServer will not be thoroughly explored simply because it's the
OpenServer OS? Is this really the position and policy of PHP as a
company?
I'm not asking these questions sarcastically and they are not intended
to provoke an argument in any way. I just need to know where I stand as
one organization to another. PHP is an integral part of our
infrastructure. I love PHP and have built many applications under it.
We've had very few problems with PHP in the past and have always been
able to resolve issues. PHP as a company and indeed a development
community has my utmost respect.
However, that being said, I can't jeopordize our organization, and I'm
sure you'll understand, by developing systems using a product that will
not be supported in the future on the operating system we are using. In
fact the current system we are replacing was originally developed under
Visual FoxPro For Unix. We rewrote that application using PHP, MySQL and
Apache for the very reason that FoxPro for unix is a dead language.
In my opinion this issue is not bogus. It may very well be a problem
with my system. I would be more inclined to agree with that synopsis if
it weren't for the fact that 4.2 doesn't have the problem and for the
fact that changes were made to the socket handling facilities starting
with 4.3, which is the starting version that exhibits the problem.
Currently I have over 600 servers in 270+ locations using 4.0.6 without
any problems. These servers have been running this version for 5 or 6
years. I would like to upgrade to a later version of PHP in order to
take advantage of some of the new functionality and since I'm upgrading
I would like to move to the most current version feasible. Maybe that
version is 4.2.3.
Thank you for your time,
Dean
------------------------------------------------------------------------
[2005-11-21 09:11:52] [EMAIL PROTECTED]
SCO isn't really OS we support (or even want to support) so you're on
your own. And this seems a lot more like a problem with your system
only.
------------------------------------------------------------------------
[2005-11-21 00:27:19] dgrimes at scvl dot com
I agreed to test it. Maybe nobody else has reported this but I still
need to figure out what the problem is and get it fixed. I'm not trying
to be obstinate. I appreciate all of the help I have received from the
folks at PHP. I was just merely pointing out that even if PHP5 works, I
won't be able to use it.
Version 4.2.x doesn't exhibit the problem. Is there a way to review the
socket related changes in 4.3.0? Something that changed on that
transition is causing this problem on both 5.0.4 and 5.0.6 OpenServer
OS's. I'm willing to try anything you guy's suggest.
I tried building with --disable-all and received the following error on
make:
.lo Zend/zend_reflection_api.lo Zend/zend_execute.lo
sapi/cgi/cgi_main.lo sapi/c
gi/getopt.lo main/internal_functions.lo -lm -lsocket -o sapi/cgi/php
Undefined first referenced
symbol in file
spl_ce_Countable ext/standard/array.o
php_pcre_replace main/SAPI.o
php_ob_gzhandler_check main/output.o
uncompress ext/standard/image.o
sapi/cgi/php: fatal error: Symbol referencing errors. No output written
to sapi/
cgi/php
collect2: ld returned 1 exit status
make: *** [sapi/cgi/php] Error 1
Thanks,
Dean
------------------------------------------------------------------------
[2005-11-21 00:05:39] [EMAIL PROTECTED]
I did not ask you to start using PHP 5, I asked to TEST it.
And use --disable-all to get as clean build as possible.
Anyway, this all seems some problem in your system alone. Nobody else
has reported any problem like this before.
------------------------------------------------------------------------
[2005-11-20 23:41:45] dgrimes at scvl dot com
I tried PHP5 but could not get a clean compile out of it yet. First I
was missing two libraries, libxml2 and libxslt and then SQLLite has
problems then PATH_MAX is not defined. I finally worked past those and
now I get errors installing to apache. There are some undefined
symbols.
Even if I did have a clean compile today, I've already completed
testing PHP4 with my current project and with our existing systems. I
just don't have time to implement PHP5 without going through all of the
documentation and testing again, which is a lot of work. I am planning
to deploy to the chain the 2nd week in January. With the holiday season
just around the corner, my work load will not permit me to alter my
design to include PHP5.
If you think that it will help troubleshoot the problem, I'll persue
PHP5 only to the extent that it will help us resolve this issue.
Here is the error when I execute make install for PHP5:
page: php-config.1
Installing PEAR environment: /usr/local/lib/php/
dynamic linker: /d/cdev/php5-200511201930/sapi/cli/php: relocation
error: symbol
not found: xmlStructuredError
make[1]: *** [install-pear-installer] Killed
make: *** [install-pear] Error 2
Thanks,
Dean
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/35292
--
Edit this bug report at http://bugs.php.net/?id=35292&edit=1
