Re: ./configure errors not reported
| From: | Richard Lynch | Date: | Tue, 12 Dec 2000 02:06:09 +0000 |
| Subject: | Re: ./configure errors not reported | ||
| References: | 1 | Groups: | php.qa |
| Request: | Send a blank email to php-qa+get-1812@lists.php.net to get a copy of this message | ||
I think arbitrary --xxx is allowed to, like, be passed on down to gcc or
somesuch...
So you'd have to test for all strings that look "like" what PHP should
accept and then error on those... That's just too ugly.
Disclaimer: At least I think that was the answer when I asked about this 2
years ago...
----- Original Message -----
From: Olivier Cahagne <cahagn_o@epita.fr>
To: php-qa <php-qa@lists.php.net>
Sent: Sunday, December 10, 2000 5:45 PM
Subject: [PHP-QA] ./configure errors not reported
> ./configure --enable-mysql
>
> won't output any error saying that this option doesn't exist, shouldn't
> it be easy to detect an error when someone mistyped a ./configure
> parameter ?
>
> Sometimes, you think you have compiled an extension because you thought
> --with-ftp was ok (instead of --enable-ftp), especially when testing PHP
> 4 for the first time as some options have changed since PHP 3.
> --
> Olivier.Cahagne@epita.fr
>
>
> --
> PHP Quality Assurance Mailing List <http://www.php.net/>
> To unsubscribe, e-mail: php-qa-unsubscribe@lists.php.net
> For additional commands, e-mail: php-qa-help@lists.php.net
> To contact the list administrators, e-mail: php-list-admin@lists.php.net
>
>