PHP 4.3 and Mac OS X
Subject:   "./configure --with" does not seems to work
Date:   2004-02-12 01:15:12
From:   jeanloui
I have followed all the steps... and those in

Downloaded php 4.3.4 (not from entropy, but the standard)
Downloaded all the Fink stuff (great!)

No errors during ./configure --with-xxx

"make install" without the old php 4.1.2 backup (sorry)

Restart the Apache and...

When I go to info.php, the 4.3.4 is running but it does not recognize all the configure commands (only '--with-apxs')

Its a strange situation, cause I'm running mysql and some php/mysql sites (PostNuke) work all right but some recent scripts stop to work...

What can be happened?

Does the "make install" create the php.ini (and place it at the appropiate dir) the or I must do something (re-place it) manually?

I have placed the "php.ini-recommended" in usr/local/lib and renamed it php.ini

I'm under Mac OS X 10.2.8 and mysql 2.3.2, Apache 1.3.29 (Darwin)


Full Threads Oldest First

Showing messages 1 through 5 of 5.

  • some advances
    2004-02-12 05:50:31  jeanloui [View]

    I have "fixed" some of this with the "BAD" php.ini option of
    register_globals = On

    (I must upgrade my scripts :(
    But still does not recognize the "--with-xxx" configures...

    He IS managing the mysql, but he does not run the gd graphic libraries (for instance)

    * Is there a way of forcing this ./configures whit declarations in php.ini ?

    * Must I ./configure --with-xxx (All libraries) again?

    * And every time that I ./configure , must I "make", "sudo make install" and change the php.ini ?? Or there is a short way for all that ??

    * Is there an istruction in ./configure for knowing internally WHAT libraries are enabled?

    You see: I still need the help!

    (and I'll post here if I fix it)

    • Adam Trachtenberg photo some advances
      2004-04-07 22:14:33  Adam Trachtenberg | O'Reilly Author [View]

      You should do a: "make clean" before you reconfigure anything if you want phpinfo() to display the correct configuration options.

      After the configure, you must do a "make," "sudo make install," and "sudo apachectl restart." The configure command only tells PHP how it should be configured when you build it using make, it doesn't make the changes itself.

      You don't need to copy or edit php.ini.
      • upgrading to 4.3.6
        2004-05-07 05:10:59  jeanloui [View]

        I have cleaned all and upgraded to 4.3.6 and builded and istalled png, jpeg and xml libraries

        Now my Configure Command looks like this:
        './configure' '--with-xml' '--with-zlib' '--with-gd' '--with-jpeg-dir=/usr/local' '--with-png-dir=/usr/local' '--with-apxs=/usr/sbin/apxs'
        and I can "imagecreate" png files!

        - I'm still running well the mysql 3.23.49 although no "--with-dbase" nor "--with-msql" configure commands appear: How is it possible?

        Thanks for all your great support!

  • error logs
    2004-02-12 02:37:10  jeanloui [View]

    I get this kind of errors in error_log:

    [error] PHP Notice: Use of undefined constant
    [error] PHP Notice: Undefined variable:
    [error] PHP Notice: Use of undefined constant http_referer - assumed

    And all this constants and variables are defined !
    Also there are 3 strange new lines:

    Processing config directory: /private/etc/httpd/users
    Processing config file: /private/etc/httpd/users/prunila.conf
    Processing config file: /private/etc/httpd/users/xavierbl.conf

    * Why is Apache checking the users dirs?

    I only want to use one ! httpd.conf at

    ... and the only good line:

    [notice] Apache/1.3.29 (Darwin) PHP/4.3.4 mod_perl/1.26 configured -- resuming normal operations
    • Adam Trachtenberg photo error logs
      2004-04-07 22:10:03  Adam Trachtenberg | O'Reilly Author [View]

      The "use of undefined constant" lines usually appear when you reference an array element inside double quotes.

      The Apache config lines are there to allow users to customize their personal home directories configuration without giving them access to the main httpd.conf file, which is owned by root. It's a feature, not a bug. I think you can disable this by editing out a few lines at the bottom of the master httpd.conf file, if it really bothers you.