DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=40653>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=40653 ------- Additional Comments From [EMAIL PROTECTED] 2006-10-06 06:26 ------- >>Feel free to contribute an alternative build tool. You'll have to deal with >>the dependencies too, of course. And bear in mind that apxs is designed to >>work in packages, where you don't have all the build debris lying around. That may explain the need to run httpd from apxs. It appeared that since apxs is created dynamically, it could at least contain all of the CFLAGS, include paths, etc. that would be required by a fairly popular external module (PHP), without reading other files. >>Anyway, cross-compiling PHP sounds to me like a *much* bigger job than this. I'm not so sure. PHP configure supports the same --host= and --target= options as Apache configure. I was able to configure and cross-compile PHP successfully, that is, until I added the --with-apxs2= option. I didn't realize that without it, the loadable module that Apache needs isn't built. Now I'm left with a cross-compiled httpd daemon that loads and runs just fine on my target platform, but with no PHP support. I appreciate the feedback. I'll probably need to revert to installing the GCC toolchain and software packages on my target platform and rerun the configure/make steps in "native" mode. I was hoping for any workaround that would allow me to avoid that. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
