note 18899 deleted from ref.pfpro by sniper

From: Date: Thu, 10 Oct 2002 00:23:19 +0000
Subject: note 18899 deleted from ref.pfpro by sniper
References: 1  Groups: php.notes 
Request: Send a blank email to php-notes+get-37873@lists.php.net to get a copy of this message
I was having problems with the PHP configuration recognizing that I had a recent version of the PFPRO SDK. I found a bug in the config.m4 file for the pfpro extension as follows - *********** PFPRO_VERSION3=nm $PFPRO_LIB_DIR/$PFPRO_LIB | awk '{print $3}' | grep ^pfpro > /dev/null && echo 1 || echo 0 PFPRO_VERSION2=nm $PFPRO_LIB_DIR/$PFPRO_LIB | awk '{print $3}' | grep ^PN > /dev/null && echo 1 || echo 0 ************ When I issued the above 'nm' statement from the UNIX command line, two bugs were apparent: 1) the awk was looking at column 3, but should have been looking at column 8 instead and 2) the caret in the grep statement was causing the command to return a failure. Here is the corrected syntax for the config.m4 file: # Changed col to 8 from 3, removed caret from grep stmts PFPRO_VERSION3=nm $PFPRO_LIB_DIR/$PFPRO_LIB | awk '{print $8}' | grep pfpro > /dev/null && echo 1 || echo 0 PFPRO_VERSION2=nm $PFPRO_LIB_DIR/$PFPRO_LIB | awk '{print $8}' | grep PN > /dev/null && echo 1 || echo 0 Once you've update the config.m4 file, you'll need to run ./buildconf before running your configure statement. Make it a point to run ./buildconf and make distclean before configuring and building PHP. It could save you a lot of heartache. Hope this helps.

« previous php.notes (#37873) next »