-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 All,
On 8/19/14, 5:45 PM, Christopher Schultz wrote: > All, > > Does anyone know if it is possible to build mod_jk on Mac OS X > given the stock httpd that comes with the OS? I don't think httpd > is installed with a stock Mavericks, but my computer is old enough > to have been upgraded from a version of Mac OS that did include it > initially. > > When I get the source distro and unpack it, configure tells me: > > $ ./configure checking build system type... > x86_64-apple-darwin13.3.0 checking host system type... > x86_64-apple-darwin13.3.0 checking target system type... > x86_64-apple-darwin13.3.0 checking for a BSD-compatible install... > /usr/bin/install -c checking whether build environment is sane... > yes > > [...] > > checking for getaddrinfo... yes checking for gethostbyname_r... no > checking for target platform... unix no apache given no netscape > given configure: error: Cannot find the WebServer > > Okay, configure can't find httpd. Configure claims that --with-apxs > will default to looking in $PATH for apxs. Let's try something: > > $ which apxs /usr/sbin/apxs > > Hmm. It's in the path. Weird configure did not find it. Oh, well: > > $ ./configure --with-apxs=`which apxs` checking build system > type... x86_64-apple-darwin13.3.0 checking host system type... > x86_64-apple-darwin13.3.0 checking target system type... > x86_64-apple-darwin13.3.0 checking for a BSD-compatible install... > /usr/bin/install -c checking whether build environment is sane... > yes checking for gawk... no checking for mawk... no checking for > nawk... no checking for awk... awk checking whether make sets > $(MAKE)... yes checking for test... /bin/test checking for grep... > /usr/bin/grep checking for echo... /bin/echo checking for sed... > /usr/bin/sed checking for cp... /bin/cp checking for mkdir... > /bin/mkdir need to check for Perl first, apxs depends on it... > checking for perl... /usr/bin/perl APRINCLUDEDIR is > -I/usr/include/apr-1 -I/usr/include/apr-1 building connector for > "apache-2.0" checking for gcc... > /Applications/Xcode.app/Contents/Developer/Toolchains/OSX10.9.xctoolchain/usr/bin/cc > > > checking for C compiler default output file name... configure: error: > C compiler cannot create executables > > That's weird... this step works okay when I don't specify apxs. > > Is this likely to be an artifact of an old httpd (and apxs) along > with a much more recent XCode (and command-line support)? > > For those who build on Mac OS, what setups have you found that were > particularly convenient? > > Thanks, -chris It looks like this was a problem with my toolchain and nothing else: reading a suggestion found on code.google.com [1] did the trick for me. It seems like Xcode is a bit broken, here, and needs a bit of a manual patch -- at least, in my case it did. I was also able to build tomcat-native after this fix as well. - -chris [1] https://code.google.com/p/modwsgi/issues/detail?id=312 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJT88xIAAoJEBzwKT+lPKRYIVIP/1HUWNldqtWdQ9eUCl+yuIkN 6/2YXCsIhY8LIrwZo0akumAbZsBWgqJhSgE8KE5qVnb3gD5CdBsPzp19FWuc6Cfd I9pnfzzPno8fB1Abd6F/lHo7nOMZ5cvM5RnPAE15ILucylUkeKlm1qS1eTQZ3wVe KcQoKFHolgx48flXG9qTzIVL82Hh0OloTg82uMp9xiyugev/VNX7efGQOlBiklLk o9clIj3b+y22EgnJ4WnOWYGS4fK8kYAkXmJJdW7FVWQrrjbe3nIlM57DF2umklw3 xup1T/dHduJCxyrCYFgEcpNBCvepjWqBxA6g0lpTPjJ+EXRiL6rvh/rG28AtlHY5 w0XtDJ1epO++uhvSnfodx29IIye3nXz2djhCTexLwtAS0ULCrftxYNHjEPXBRwkE 89MZfyHggXBl0d5mL2hzGzXDkz9h6se4sKzJ45V8yRCFiu2iKkmkJsxi/u7xEx3b CF3mYvseNsfQn/zRwuNAOMQvkW8v904kJa93uhhUQvQ49+RiwTQkYYWZIUP36RhY JfvxCDUglqCA7/mJJHUlmaVXMR0/IHUPcZE2EHW1E6f1mWUbgqfL8FVsch6UGLX8 tEUUGpoYnSFvf2SwSZKllKzBBP0BSgwUAueYpHpg2rgBlMsvJbq54+sD0rqtrsrp sWgrio+/KNIqPnWSoN1O =fBPh -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
