Re: Problem with -c option and --with-config-file-path option
| From: | Rasmus Lerdorf | Date: | Fri, 28 Mar 2003 06:27:24 +0000 |
| Subject: | Re: Problem with -c option and --with-config-file-path option | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-402@lists.php.net to get a copy of this message | ||
Hey, J2EE/DB2 has a php.ini file? Cool.
This is the wrong list for this question, but you could try using the
PHPRC env var instead to set the location of your php.ini file.
-Rasmus
On Thu, 27 Mar 2003, Mark Striebeck wrote:
> Hi,
>
> we are building PHP with the --with-config-file-path compile setting to get our php.ini file
> from our own location.
>
> Now, in some scenarios we need to run PHP with the -c command line option to get the php.ini
> file from a different location.
>
> This seems to cause problems!
>
> When using the -c command line option, our PHP files cannot find their includes anymore.
>
> My last attempt was to set the -c command line option to the exact same location that we use
> for the --with-config-file-path compile setting. With the same result: without the -c option
> everything works, with the -c setting the include files are not found.
>
> What are the differences between these two options? Does the -c have any other side effects?
>
> Thanks
> MarkS
>
> ---------------------------------------------------
> Mark Striebeck SourceForge Engineering Manager
> VA Software http://www.vasoftware.com
>
>
>
>
>