Return-Path: X-Original-To: apmail-httpd-users-archive@www.apache.org Delivered-To: apmail-httpd-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2EEA0108FE for ; Fri, 27 Feb 2015 21:49:33 +0000 (UTC) Received: (qmail 95797 invoked by uid 500); 27 Feb 2015 21:49:29 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 95754 invoked by uid 500); 27 Feb 2015 21:49:29 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 95744 invoked by uid 99); 27 Feb 2015 21:49:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Feb 2015 21:49:29 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of fduartej@gmail.com designates 209.85.215.41 as permitted sender) Received: from [209.85.215.41] (HELO mail-la0-f41.google.com) (209.85.215.41) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Feb 2015 21:49:25 +0000 Received: by labhv19 with SMTP id hv19so1265825lab.5 for ; Fri, 27 Feb 2015 13:49:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=lUcsJ04Eo4lMrM/6HLWYhA92GRzUF0DZtvG3xzfo2vU=; b=prR97Vzh5J7M8wbzExlydA2gVvcQY6s3soZqCz6cwp1dHCV0pH0SKcREU9yBclk3Qu Fy3xxLfYrZzWJV7Qipzxcnle07tvFCFBi03t7rL8Jv1wdsQIN00VIRDEZPjAqY6g7Hsb ae6McEiM/whRNaT2OgIAGvQKx1kmU8ivCn8u5WgTgc2vqBX5v8vQuIl2b5+rTKhPYuXs 1LHN5YDFUUDFfKUli+AdAWKSPauDzwSb66ARduZdvNeD3XczqweXh8Anxp3v07OOjmKE tejezFAZhvGMhaFSvTu6ciCUjKV16EsqJxXQMd8ni7aIVnHjuoU7mRqx1ZDi8qIRqHN8 15Rw== MIME-Version: 1.0 X-Received: by 10.152.36.37 with SMTP id n5mr2374879laj.40.1425073744623; Fri, 27 Feb 2015 13:49:04 -0800 (PST) Received: by 10.112.97.35 with HTTP; Fri, 27 Feb 2015 13:49:04 -0800 (PST) In-Reply-To: References: <1424448230.12650.12.camel@awang.ptcnet.ptc.com> <54F0ACD8.7050505@ptc.com> <54F0B962.1040202@ptc.com> Date: Fri, 27 Feb 2015 16:49:04 -0500 Message-ID: From: Fred Duarte To: users@httpd.apache.org Content-Type: multipart/alternative; boundary=089e0160a97e53c070051018d656 X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] building httpd 2.4 on windows x64 --089e0160a97e53c070051018d656 Content-Type: text/plain; charset=UTF-8 Unsuscribe 2015-02-27 14:09 GMT-05:00 Jeff Trawick : > On Fri, Feb 27, 2015 at 1:37 PM, Andy Wang wrote: > >> On 02/27/2015 12:09 PM, Jeff Trawick wrote: >> >>> I need to update apr-util's README.cmake file with this blurb from >>> httpd. Does this fix your issue? >>> >>> OpenSSL >>> ------- >>> >>> If you have a binary install of OpenSSL in a well-known directory (e.g., >>> %HOME%\OpenSSL-Win64) and you wish to build httpd against a different >>> install of OpenSSL, the cmake build may unexpectedly select OpenSSL >>> libraries in the well-known directory even if the expected include files >>> are used. Check the cmake output from your httpd build to confirm that >>> the expected OpenSSL libraries and include files are used. >>> >>> The cmake FindOpenSSL module searches for OpenSSL libraries in a "VC" >>> subdirectory of the OpenSSL install with filenames that indicate the >>> build >>> type (e.g., "/lib/VC/ssleay32MD.lib"); defining >>> CMAKE_PREFIX_PATH >>> or OPENSSL_ROOT_DIR or even OPENSSL_LIBRARIES does not circumvent finding >>> these libraries. >>> >>> To work around this issue, rename the well-known OpenSSL directory while >>> building httpd. Let us know if you find a better solution. >>> >>> >> Yes and no. I saw that in the httpd blurb and tried to wrap my head >> around it. >> >> I don't have a well-known openssl install so cmake isn't even finding an >> openssl install. So the first paragraph of that blurb (I think?) doesn't >> apply to me. >> >> I tried setting OPENSSL_ROOT_DIR, but I think I misunderstood the second >> paragraph. I misinterpreted the VC bit. I'll try putting the lib files in >> my openssl_root_dir/lib/VC and see if I can make that work. >> > > I doubt that would be useful, although it is where the odd FindOPENSSL > implementation will look. > > Did you set OPENSSL_ROOT_DIR on the cmake command-line, as > -DOPENSSL_ROOT_DIR=c:\Users\Foo\install\openssl_1.0.1 or similar? > > > > > >> >> Thanks, >> Andy >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org >> For additional commands, e-mail: users-help@httpd.apache.org >> >> > > > -- > Born in Roswell... married an alien... > http://emptyhammock.com/ > > -- Regards, Fred Duarte --089e0160a97e53c070051018d656 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Unsuscribe

2015-02-27 14:09 GMT-05:00 Jeff Trawick <trawick@gmail= .com>:
On Fri, Feb 27, 2015 at = 1:37 PM, Andy Wang <awang@ptc.com> wrote:
On 02/27/2015 12:09 PM, Jeff Trawick wrote:
I need to update apr-util's README.cmake file with this blurb from
httpd.=C2=A0 Does this fix your issue?

OpenSSL
-------

If you have a binary install of OpenSSL in a well-known directory (e.g., %HOME%\OpenSSL-Win64) and you wish to build httpd against a different
install of OpenSSL, the cmake build may unexpectedly select OpenSSL
libraries in the well-known directory even if the expected include files are used.=C2=A0 Check the cmake output from your httpd build to confirm tha= t
the expected OpenSSL libraries and include files are used.

The cmake FindOpenSSL module searches for OpenSSL libraries in a "VC&q= uot;
subdirectory of the OpenSSL install with filenames that indicate the build<= br> type (e.g., "<PREFIX>/lib/VC/ssleay32MD.lib"); defin= ing CMAKE_PREFIX_PATH
or OPENSSL_ROOT_DIR or even OPENSSL_LIBRARIES does not circumvent finding these libraries.

To work around this issue, rename the well-known OpenSSL directory while building httpd.=C2=A0 Let us know if you find a better solution.


 Yes and no.=C2=A0 I saw that in the httpd blurb and tried to wrap my head a= round it.

I don't have a well-known openssl install so cmake isn't even findi= ng an openssl install.=C2=A0 So the first paragraph of that blurb (I think?= ) doesn't apply to me.

I tried setting OPENSSL_ROOT_DIR, but I think I misunderstood the second pa= ragraph.=C2=A0 I misinterpreted the VC bit.=C2=A0 I'll try putting the = lib files in my openssl_root_dir/lib/VC and see if I can make that work.

I doubt that would be useful, although it= is where the odd FindOPENSSL implementation will look.

Did you set OPENSSL_ROOT_DIR on the cmake command-line, as -DOPENSSL_= ROOT_DIR=3Dc:\Users\Foo\install\openssl_1.0.1 or similar?



=C2=A0

Thanks,
Andy


-------------------------------------------------------------= --------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org




--
Born in Roswell... married an alien...
http://emptyhammock.com/

<= /div>



--
Regards,
Fred Duarte
--089e0160a97e53c070051018d656--