Opened 19 years ago
Closed 19 years ago
#8831 closed defect (fixed)
new apache2 2.2.2 does not build under mac intel
| Reported by: | edko@… | Owned by: | james@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.2 |
| Keywords: | Cc: | ||
| Port: |
Description
Apache2 2.2.2_2 does not build under mac os x 10.4 intel on a macbook pro. The port will build under a 10.4 ppc G5. Possible difference between the two machines is the number of ports installed on each; the G5 has a very small number of installed ports.
Attachments (1)
Change History (4)
comment:1 Changed 19 years ago by edko@…
| Owner: | changed from darwinports-bugs@… to james@… |
|---|
Changed 19 years ago by edko@…
| Attachment: | apache2_build_errors.txt added |
|---|
comment:2 Changed 19 years ago by james@…
I don't have an Intel Mac to test on, so I can't fix this - however...
it looks like the configure step is failing. This might be because it's trying to detect darwin, thinking it's a ppc and telling gcc this is the case - or, worse, it's detecting an intel chip and thinking it's not darwin at all, therefore not being able to find any files...
Ed - can you navigate into the build directory and upload configure.log ?
thanks!
comment:3 Changed 19 years ago by edko@…
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I believe I found the problem in my specific case. It appears that installing the port libhttpd creates a file '/opt/local/include/httpd.h' which will trip up the apache2 build. I solved my problem by deactivating the port libhttpd.
Is there a mechanism within Darwinports to flag incompatible ports? Perhaps something which would detect incompatible ports and then error out with an appropriate message?
Ed - can you navigate into the build directory and upload configure.log ?
thanks!
output of build attempt