#16478 closed defect (fixed)
php5 without apache or apache2 does not compile
Reported by: | cod3monk (Julian) | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.6.0 |
Keywords: | Cc: | jyrkiwahlstedt | |
Port: | php5 |
Description
Actualy I want to install scapy, but it requires php5 (through libdnet). The problem is that php5 does not install without apache or apache2, which I definelty do not want.
Configuring SAPI modules checking for AOLserver support... no checking for Apache 1.x module support via DSO through APXS... configure: error: You have enabled Apache 1.3 support while your server is Apache 2. Please use the appropiate switch --with-apxs2 Error: The following dependencies failed to build: py-pylibpcap swig php5 python25 ruby py-readline Error: Status 1 encountered during processing.
building php5 with -apache and -apache2 does not help.
Change History (7)
comment:1 Changed 16 years ago by cod3monk (Julian)
Cc: | codemonk@… added |
---|
comment:2 Changed 16 years ago by blb@…
Cc: | jwa@… added; codemonk@… removed |
---|---|
Owner: | changed from macports-tickets@… to ryandesign@… |
Port: | php5 added |
Assigning to/Cc'ing maintainers.
comment:3 Changed 16 years ago by ryandesign (Ryan Carsten Schmidt)
Status: | new → assigned |
---|
Yes, I am aware of the problem and will fix it. This is a new problem as of Mac OS X Leopard. For now your only option is to build with the +apache2 or +fastcgi variant, even if you do not want Apache 2 or FastCGI support. +fastcgi will build quicker since it does not have any additional dependencies, while +apache2 will build the apache2 port first. I will change the ports so that +apache2 is the default, since that is the most popular option, but there will also be a new variant +no_web to build without any web server support.
comment:4 Changed 16 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Fixed in r39862. Now +apache2 is the default, since that's the most popular and the only Apache variant that works on Leopard right now. You can still select +apache if you want Apache 1 support instead (on Tiger or earlier), or +fastcgi if you want FastCGI support instead (or in addition). If you want no web server support at all, then there's a new variant +no_web. Thanks again for reporting the problem.
Cc Me!