ID:               33533
 Updated by:       [EMAIL PROTECTED]
 Reported By:      scott dot barnett at thuringowa dot qld dot gov dot au
-Status:           Open
+Status:           Feedback
 Bug Type:         PDO related
 Operating System: CentOS 4.1 / Redhat Enterprise 4
 PHP Version:      5CVS-2005-07-04
 New Comment:

Thank you for this bug report. To properly diagnose the problem, we
need a backtrace to see what is happening behind the scenes. To
find out how to generate a backtrace, please read
http://bugs.php.net/bugs-generating-backtrace.php

Once you have generated a backtrace, please submit it to this bug
report and change the status back to "Open". Thank you for helping
us make PHP better.




Previous Comments:
------------------------------------------------------------------------

[2005-07-13 01:36:18] scott dot barnett at thuringowa dot qld dot gov
dot au

Thanks wez, I've got PDO-ODBC working now with snapshot
php5-200507122030.

If I use PDO this shows up in err_log:
FATAL:  emalloc():  Unable to allocate -2147483648 bytes
FATAL:  emalloc():  Unable to allocate -2147483648 bytes
FATAL:  emalloc():  Unable to allocate -2147483648 bytes

If I use the ifx_ functions this shows up in err_log:
[Wed Jul 13 09:26:51 2005] [notice] child pid 15980 exit signal
Segmentation fault (11)
[Wed Jul 13 09:26:51 2005] [notice] child pid 15981 exit signal
Segmentation fault (11)

Same problems basically, only happens when querying Informix text
fields, char and int are fine.

------------------------------------------------------------------------

[2005-07-12 12:57:32] [EMAIL PROTECTED]

Remove old stuff:

- pear uninstall pdo_odbc
- pear uninstall pdo

Grab a PHP 5.1 snapshot from http://snaps.php.net:

- Extract it
- cd into the dir
- ./configure <your usual options> --with-pdo-odbc=unixODBC
- make
- make install

then test it

------------------------------------------------------------------------

[2005-07-12 07:40:11] scott dot barnett at thuringowa dot qld dot gov
dot au

Rightio, it was user error. I did an strace and I had php.ini in the
wrong place, I've corrected it. Previously I configured the extensions
dir as a configure option and compiled my own pdo.so and pdo_odbc.so so
it worked ok.

"php -m" shows up PDO and pdo_sqlite. I thought PDO was going to be
included with PHP and therefore would be in the latest snapshot or do
you want me to get it from pear?

------------------------------------------------------------------------

[2005-07-12 06:20:34] scott dot barnett at thuringowa dot qld dot gov
dot au

Argh scratch the comment about the .so's being in the source tree.
They're there because I put them there when I was compiling the
previous version.

Just for good measure I completely removed apache from the system,
removed the source trees, and started from scratch. Still experiencing
the same problem though.

Tried
pear install -f PDO
pear install -f PDO_ODBC

"pear list" now shows up:
Installed packages:
===================
Package              Version State
Archive_Tar          1.1     stable
Console_Getopt       1.2     stable
HTML_Template_IT     1.1     stable
Net_UserAgent_Detect 2.0.1   stable
PDO                  0.3     beta
PDO_ODBC             0.2     beta
PEAR                 1.3.5   stable
XML_RPC              1.3.1   stable

PDO still comes back with "Failed to connect:could not find driver"

------------------------------------------------------------------------

[2005-07-12 05:57:02] scott dot barnett at thuringowa dot qld dot gov
dot au

Yeah it was a clean build, and I definately have both extensions in
php.ini. Now that it's not a pear library, is there something I need to
add to my configure syntax to include pdo unixODBC support?

I've done a find -name pdo.so and it only shows up in the source tree
that I compiled PHP from. pdo_odbc.so also shows up in that tree.

Trying with the new snapshot, php -m shows up:

[PHP Modules]
ctype
date
dom
ftp
iconv
informix
ldap
libxml
mysql
odbc
pcre
PDO
pdo_sqlite
pgsql
posix
session
SimpleXML
sockets
SPL
SQLite
standard
tokenizer
xml

------------------------------------------------------------------------

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/33533

-- 
Edit this bug report at http://bugs.php.net/?id=33533&edit=1

Reply via email to