Re: [Openvpn-users] Building OpenVPN in MinGW

[James Yonan <jim@xxxxxxxxx>]

On Wed, 2 Mar 2005, Mathias Sundman wrote:

> On Wed, 2 Mar 2005, James Yonan wrote:
> 
> >> So in OpenVPN's makefile.w32 I had to change
> >>
> >> OPENSSL = /c/src/openssl-0.9.7e
> >> LIB_DIRS = -L${OPENSSL}/out -L${LZO}
> >> to
> >> OPENSSL = /c/OpenSSL
> >> LIB_DIRS = -L${OPENSSL}/lib/MinGW -L${LZO}
> >>
> >> Even after these changes I got the following compile error:
> >>
> >> c:\MinGW\bin\..\lib\gcc\mingw32\3.4.2\..\..\..\..\mingw32\bin\ld.exe:
> >> cannot find -lssl32
> >>
> >> To get around this problem, I renamed ssleay32.a to libssl32.a. Then it
> >> found the library.
> >>
> >> Q1: Why did I have to rename ssleay32.a? It doesn't seem like the "right"
> >> way to solve the problem.
> >>
> >>
> >> Then the linking failed because it couldn't find the lzo library.
> >>
> >> I changed
> >> LZO = /c/src/lzo-1.08
> >> to
> >> LZO = ../lzo-1.08
> >>
> >> which was the correct path in my installation, but I found that the libs
> >> were created in the src/.libs dir, so I changed
> >>
> >> LIB_DIRS = -L${OPENSSL}/lib/MinGW -L${LZO}
> >> to
> >> LIB_DIRS = -L${OPENSSL}/lib/MinGW -L${LZO}/src/.libs
> >>
> >> and openvpn.exe could finaly be built.
> >>
> >> Q2: Did I do anything wrong while building LZO, or why did I have to
> >> change the path to the lzo library in LIB_DIRS?
> >>
> >> James, what do you think about changing makefile.w32 to match a default
> >> installtion of the binary OpenSSL distribution instead of the source
> >> distribuition? I think very few windows users have any use for the OpenSSL
> >> source, so they could avoid going through the trouble with building
> >> OpenSSL just to build OpenVPN.
> >
> > Are you using this page to get the binary distro? :
> >
> > http://www.openssl.org/related/binaries.html
> 
> Yes.
> 
> > The problem I have with this is that it's a third party providing the
> > build, not the OpenSSL project itself.  I would rather build OpenVPN from
> > official OpenSSL sources.  I agree that it makes the build process more
> > complex, but then this should not be an issue except for developers.
> 
> Okay, how about just adding a few lines about that the above changes to 
> makefile.w32 are necessary to build OpenVPN using the binary distribution 
> of OpenSSL to Install-Win32?

I agree.  Can you make a patch to makefile.w32 that adds comments 
to that effect?

> Do you have any clues about the other questions?

On Q1, isn't it just a matter of gcc wanting to find lib[-l argument].a?

I think Q2 might be related to the fact that there are two ways to build
LZO on Windows:

(a) Follow the specific Win32 build instructions.
(b) Run ./configure from MinGW/MSYS shell.

There are subtle differences in the result of both methods, such as where
the libraries are build.  The current makefile.w32 assumes (a).

James


____________________________________________
Openvpn-users mailing list
Openvpn-users@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/openvpn-users