apache fails to build with clang

[essandess (Steve Smith)]

:info:build /usr/bin/clang -L/opt/local/lib -Wl,-headerpad_max_install_names -arch x86_64 
-bundle -undefined suppress -flat_namespace  -o libproxy.so mod_proxy.lo proxy_cache.lo pr
oxy_connect.lo proxy_ftp.lo proxy_http.lo proxy_util.lo 
:info:build duplicate symbol _ap_os_is_path_absolute in:
:info:build     mod_proxy.lo
:info:build     proxy_cache.lo
:info:build duplicate symbol _ap_os_is_path_absolute in:
:info:build     mod_proxy.lo
:info:build     proxy_connect.lo
:info:build duplicate symbol _ap_os_is_path_absolute in:
:info:build     mod_proxy.lo
:info:build     proxy_ftp.lo
:info:build duplicate symbol _ap_os_is_path_absolute in:
:info:build     mod_proxy.lo
:info:build     proxy_http.lo
:info:build duplicate symbol _ap_os_is_path_absolute in:
:info:build     mod_proxy.lo
:info:build     proxy_util.lo
:info:build ld: 5 duplicate symbols for architecture x86_64
:info:build clang: error: linker command failed with exit code 1 (use -v to see invocation
)
:info:build make[4]: *** [libproxy.so] Error 1

[mf2k (Frank Schima)]

It is not useful to Cc openmaintainer@….

[ryandesign (Ryan Carsten Schmidt)]

Do you really need to build Apache version 1? Apache version 2, in the apache2 port, builds fine on Mavericks.

[essandess (Steve Smith)]

Perhaps not -- I'm trying to install mod_perl and and apache is a dependency. I'll look into alternate options.

[ryandesign (Ryan Carsten Schmidt)]

Try the mod_perl2 port instead, which uses apache2.

[jmroot (Joshua Root)]

Looks like inlining gone awry, so maybe -std=gnu89 will help?

[jeremyhu (Jeremy Huddleston Sequoia)]

Yeah, this doesn't look Mavericks related...

[mina.macports@…]

For those of us stuck with apache1 legacy systems, I can confirm -std=gnu89 allows compilation to succeed

[Ionic (Mihai Moldovan)]

r128950.

[Ionic (Mihai Moldovan)]

And follow-up revbump in r128962.

[ryandesign (Ryan Carsten Schmidt)]

If the problem was a build failure, why would a revbump be necessary?

If you resolve a ticket, please assign the ticket to yourself or at least Cc yourself so that you're in the loop for any follow-up conversation.

[Ionic (Mihai Moldovan)]

Replying to ryandesign@…:

If the problem was a build failure, why would a revbump be necessary?

Because the commit inserts patches which change the behavior generally (replacing -undefined suppress -flat_namespace linker options with -undefined dynamic_lookup), catches a clash with the libc's readline function and adds -std=c89 to CFLAGS.

Users having the port currently installed (on Tiger and below?) would have a diverging version of the port. But consistency is key!

If you resolve a ticket, please assign the ticket to yourself or at least Cc yourself so that you're in the loop for any follow-up conversation.

Sorry, I hope you don't mind me hijacking your ticket. It was stale for so long and I needed apache(1) to at least build successfully for another port update depending on apache(1).

[ryandesign (Ryan Carsten Schmidt)]

Replying to ionic@…:

Because the commit inserts patches which change the behavior generally (replacing -undefined suppress -flat_namespace linker options with -undefined dynamic_lookup),

Ah, ok. That's a good reason. I didn't look at the patch closely enough.

Users having the port currently installed (on Tiger and below?) would have a diverging version of the port. But consistency is key!

Yes. Note that Tiger is the earliest version on which MacPorts runs.

Sorry, I hope you don't mind me hijacking your ticket. It was stale for so long and I needed apache(1) to at least build successfully for another port update depending on apache(1).

Not at all, I appreciate you fixing it.

[Ionic (Mihai Moldovan)]

Replying to ryandesign@…:

Not at all, I appreciate you fixing it.

Fixing*.

---

* I have not tested if it actually runs correctly. Or starts up. Or does anything. Chances are it works, but all bets are off.

[Ionic (Mihai Moldovan)]

Replying to ionic@…:

Replying to ryandesign@…:

Not at all, I appreciate you fixing it.

Fixing*.

---

* I have not tested if it actually runs correctly. Or starts up. Or does anything. Chances are it works, but all bets are off.

Ok... It starts up, can serve a simple, static "It works!" webpage and can be turned off again. But that's as far as I'll go regarding testing apache(1).