Someone else replied off-list that 2.2.13 works with OpenSSL 1.0.0 beta, and that there's a patch for 2.2.12 that works as well.
2.2.13 does appear to, though there's one remaining issue: -DHAVE_OPENSSL still wasn't getting defined. I added -DHAVE_OPENSSL to my $CC, and things built, and I can list http and https URL's in subversion now. This despite #define HAVE_OPENSSL being in ap_config_auto.h. Thanks folks! On Mon, Aug 10, 2009 at 10:38 AM, Dan Stromberg<[email protected]> wrote: > Someone replied off-list that 2.2.13 should help. > > I'm finding that while 2.2.13 probably is a better version, I still get: > > In file included from ssl_private.h:60, > from mod_ssl.c:27: > ssl_toolkit_compat.h:254:2: error: #error "Unrecognized SSL Toolkit!" > In file included from ssl_private.h:62, > from mod_ssl.c:27: > ssl_util_ssl.h:78: error: expected â )â before â *â token > ssl_util_ssl.h:79: error: expected â )â before â *â token > ssl_util_ssl.h:80: error: expected â =â , â ,â , â ;â , > â asmâ or â __attribute__â before â *â token > ssl_util_ssl.h:81: error: expected â =â , â ,â , â ;â , > â asmâ or â __attribute__â before â *â token > ssl_util_ssl.h:82: error: expected â )â before â *â token > ssl_util_ssl.h:83: error: expected â =â , â ,â , â ;â , > â asmâ or â __attribute__â before â *â token > ssl_util_ssl.h:84: error: expected â )â before â *â token > > Any other suggestions? > > On Mon, Aug 10, 2009 at 10:08 AM, Dan > Stromberg<[email protected]> wrote: >> It seems that building Apache 2.2.12 from source against OpenSSL 1.0.0 >> beta 3 (also built from source) on an openSUSE 10.3 system that has >> rpm's of older Apache and OpenSSL, yields a build failure - maybe >> because of the dual OpenSSL, maybe not. >> >> Is this a known issue? >> >> Is there a fix? >> >> I've googled and googled, and found nothing but questions. OK, there >> were answers, but they were of the "Are you sure you installed >> OpenSSL?" or "Why not use rpm's?" variety, while I have 2 OpenSSL's >> not 0, and I can't use rpm's due to the oldness of the OS I must build >> on and for. >> >> It seems like mod_ssl.c isn't #include'ing ap_config_auto.h directly >> or indirectly, so naturally HAVE_OPENSSL isn't #define'd. >> >> Thanks! >> >> On Mon, Aug 10, 2009 at 9:27 AM, Dan Stromberg<[email protected]> >> wrote: >>> I'm puzzled now. >>> >>> OpenSSL is either building fine, or building with a problem that has >>> no corresponding error message. Yes, I have the OpenSSL 1.0.0 beta 3 >>> tarball - that's what allowed me to build it without an error message. >>> >>> It's not until I try to build apache against that OpenSSL that I get an >>> error. >>> >>> I have no OpenSSL (build) folder, though I do have an >>> openssl-1.0.0-beta3 folder (actually, I automatically renamed it to >>> src, but that's what it's called in the tarball) - is that what you >>> mean? >>> >>> I have quite a bit of experience doing the usual GNU autoconf stuff. >>> However, OpenSSL doesn't appear to be the usual autoconf stuff, and >>> apache appears to be the most complex autoconf'd package I've seen. >>> >>> I've read through apache's ./configure --help a few times recently, >>> though nothing obvious is jumping out at me about this error. It >>> kinda feels like a build bug - it shouldn't be telling me I have no >>> OpenSSL when I have 1.5 or 2 versions on my system. >>> >>> I think I neglected to mention: When doing web searches on this topic, >>> I get a decent number of hits - but they're all unanswered questions. >>> >>> On Sun, Aug 9, 2009 at 12:33 AM, Igor Cicimov<[email protected]> wrote: >>>> Did you read the README and INSTALL files in the OpenSSL folder (I assume >>>> you have openssl tarball downloaded)? They usually explain what and how to >>>> use in the ./configure and make commands. Read the help pages for configure >>>> and make too. >>>> >>>> On Sat, Aug 8, 2009 at 11:17 AM, Dan Stromberg <[email protected]> >>>> wrote: >>>>> >>>>> The subject line summarizes the issue pretty well. Following are the >>>>> details: >>>>> >>>>> The problem stems, of course, from the new packages I'm building on an >>>>> old OS. I don't have much choice in the matter though - these are the >>>>> constraints I must operate within. >>>>> >>>>> I want to have two versions of OpenSSL on the system in question - one >>>>> that comes with OS, and one for a new apache and subversion. >>>>> >>>>> I've tried both with OpenSSL 0.9.8k and OpenSSL 1.0.0 beta 3. This >>>>> message will cover the specifics of the situation with 1.0.0 beta 3. >>>>> >>>>> I'm using the following small script to configure and build against >>>>> OpenSSL 1.0.0 beta 3: >>>>> >>>>> export PATH=/usr/local/svn/bin:$PATH >>>>> CC="gcc -I/usr/local/svn/include -L/usr/local/svn/lib -Wl,-rpath >>>>> -Wl,/usr/local/svn/lib" ./configure --prefix=/usr/local/svn >>>>> --enable-modules=all --enable-ssl --with-ssl=/usr/local/svn && make -j >>>>> 1 >>>>> >>>>> With this script in place, the apache build chugs along for a while, >>>>> and then gives copious errors starting with: >>>>> >>>>> make[3]: Entering directory >>>>> `/data/swbuild/da_build/src/apache2/src/modules/ssl' >>>>> /usr/local/svn/build-1/libtool --silent --mode=compile gcc >>>>> -I/usr/local/svn/include -L/usr/local/svn/lib -Wl,-rpath >>>>> -Wl,/usr/local/svn/lib -g -O2 -pthread -DLINUX=2 -D_REENTRANT >>>>> -D_GNU_SOURCE >>>>> -I/data/swbuild/da_build/src/apache2/src/srclib/pcre -I. >>>>> -I/data/swbuild/da_build/src/apache2/src/os/unix >>>>> -I/data/swbuild/da_build/src/apache2/src/server/mpm/prefork >>>>> -I/data/swbuild/da_build/src/apache2/src/modules/http >>>>> -I/data/swbuild/da_build/src/apache2/src/modules/filters >>>>> -I/data/swbuild/da_build/src/apache2/src/modules/proxy >>>>> -I/data/swbuild/da_build/src/apache2/src/include >>>>> -I/data/swbuild/da_build/src/apache2/src/modules/generators >>>>> -I/data/swbuild/da_build/src/apache2/src/modules/mappers >>>>> -I/data/swbuild/da_build/src/apache2/src/modules/database >>>>> -I/usr/local/svn/include/apr-1 >>>>> -I/data/swbuild/da_build/src/apache2/src/server >>>>> -I/data/swbuild/da_build/src/apache2/src/modules/proxy/../generators >>>>> -I/usr/local/svn/include >>>>> -I/data/swbuild/da_build/src/apache2/src/modules/ssl >>>>> -I/data/swbuild/da_build/src/apache2/src/modules/dav/main >>>>> -prefer-non-pic -static -c mod_ssl.c && touch mod_ssl.lo >>>>> In file included from ssl_private.h:60, >>>>> from mod_ssl.c:27: >>>>> ssl_toolkit_compat.h:254:2: error: #error "Unrecognized SSL Toolkit!" >>>>> In file included from ssl_private.h:62, >>>>> from mod_ssl.c:27: >>>>> ssl_util_ssl.h:78: error: expected â EURO ~)â EURO (tm) before â EURO >>>>> ~*â EURO (tm) token >>>>> ssl_util_ssl.h:79: error: expected â EURO ~)â EURO (tm) before â EURO >>>>> ~*â EURO (tm) token >>>>> >>>>> The key part seeming to #error "Unrecognized SSL Toolkit". >>>>> >>>>> Line 254 of ssl_toolkit_compat.h is (and is surrounded by): >>>>> >>>>> #else /** ! HAVE_OPENSSL && ! HAVE_SSLC */ >>>>> >>>>> #error "Unrecognized SSL Toolkit!" >>>>> >>>>> #endif /* ! HAVE_OPENSSL && ! HAVE_SSLC */ >>>>> >>>>> IOW, it appears thtat HAVE_OPENSSL isn't defined, even though I have >>>>> 1.5 versions (I mv'd /usr/include/openssl to >>>>> /usr/include/openssl.nopers) on the system. Also, >>>>> include/ap_config_auto.h have HAVE_OPENSSL #define'd to 1. >>>>> >>>>> But if I cut and paste the libtool command for compiling mod_ssl.c, >>>>> addnig a -E to it to get just the cpp output, it appears that >>>>> ap_config_auto.h isn't getting #include'd. >>>>> >>>>> Something's clearly going wrong with the build. Maybe it's because >>>>> I'm doing something a little bit hackish setting that weird $CC, >>>>> though that's worked well for me in the past. >>>>> >>>>> What do I need to do to build the latest apache aganist the latest >>>>> OpenSSL on openSUSE 10.3? >>>>> >>>>> Thanks! >>>>> >>>>> --------------------------------------------------------------------- >>>>> The official User-To-User support forum of the Apache HTTP Server Project. >>>>> See <URL:http://httpd.apache.org/userslist.html> for more info. >>>>> To unsubscribe, e-mail: [email protected] >>>>> " from the digest: [email protected] >>>>> For additional commands, e-mail: [email protected] >>>>> >>>> >>>> >>> >> >
