Re: [Openvpn-devel] bugfix2.1: automake support for plugin build

2011-01-06 Thread Matthias Andree
Am 07.01.2011 00:12, schrieb Mr Dash Four: > >> If the patch is applied, the libtoolize tool has populated m4/* and you've >> regenerated the aclocal.m4 with aclocal, the configure and Makefile.in, then >> it >> should suffice, yes. >> > I am more than willing to send you my spec file for you

Re: [Openvpn-devel] bugfix2.1: automake support for plugin build

2011-01-06 Thread Mr Dash Four
Can you toss your .spec file around? Just sent privately!

Re: [Openvpn-devel] bugfix2.1: automake support for plugin build

2011-01-06 Thread Mr Dash Four
If the patch is applied, the libtoolize tool has populated m4/* and you've regenerated the aclocal.m4 with aclocal, the configure and Makefile.in, then it should suffice, yes. I am more than willing to send you my spec file for you to look at and can also attach instructions on how to try to

Re: [Openvpn-devel] bugfix2.1: automake support for plugin build

2011-01-06 Thread Matthias Andree
Am 06.01.2011 23:59, schrieb Mr Dash Four: > >> This has gone wrong. The plugins should be built from the top-level >> directory instead (see below how it works for me), with the regular >> "make" that also builds openvpn, so the "for plugin in ... make -C >> $plugin ..." is no longer needed for

Re: [Openvpn-devel] bugfix2.1: automake support for plugin build

2011-01-06 Thread Mr Dash Four
This has gone wrong. The plugins should be built from the top-level directory instead (see below how it works for me), with the regular "make" that also builds openvpn, so the "for plugin in ... make -C $plugin ..." is no longer needed for these two guys. I just removed the loop to see if it

Re: [Openvpn-devel] bugfix2.1: automake support for plugin build

2011-01-06 Thread Matthias Andree
Am 06.01.2011 23:07, schrieb Mr Dash Four: > >> This has gone wrong. The plugins should be built from the top-level >> directory instead (see below how it works for me), with the regular >> "make" that also builds openvpn, so the "for plugin in ... make -C >> $plugin ..." is no longer needed for

Re: [Openvpn-devel] bugfix2.1: automake support for plugin build

2011-01-06 Thread Mr Dash Four
This has gone wrong. The plugins should be built from the top-level directory instead (see below how it works for me), with the regular "make" that also builds openvpn, so the "for plugin in ... make -C $plugin ..." is no longer needed for these two guys. "make install" should load the materia

Re: [Openvpn-devel] bugfix2.1: automake support for plugin build

2011-01-06 Thread Matthias Andree
Am 06.01.2011 21:42, schrieb Mr Dash Four: > >> I suppose you need to modify the .spec file to make sure you're running >> autoreconf twice up front (or libtoolize, aclocal, autoconf, automake, >> possibly autoheader). >> >> Note you'll want to remove the .la files from the destdir, and list the >

Re: [Openvpn-devel] bugfix2.1: automake support for plugin build

2011-01-06 Thread Mr Dash Four
I suppose you need to modify the .spec file to make sure you're running autoreconf twice up front (or libtoolize, aclocal, autoconf, automake, possibly autoheader). Note you'll want to remove the .la files from the destdir, and list the .so files in the %files section, /usr/lib/openvpn/*.so mig

Re: [Openvpn-devel] bugfix2.1: automake support for plugin build

2011-01-06 Thread Mr Dash Four
This is the patch series for the bugfix2.1 branch. I will send a separate patch pair for beta 2.2 soon. Looking for feedback, review, and ACK or NAK :-) I take it that these patches could be applied to the 2.1.4 version tree, right? If so, I would be able to test this tonight (including c

[Openvpn-devel] bugfix2.1: automake support for plugin build

2011-01-06 Thread Matthias Andree
Greetings, following up the "[OpenVPN 2.1.4 BUG]: hard-coded values in Makefiles for down-root and auth-pam plugins prevent cross compilation" bug, I am providing patches for review and test in cross-compilation environments. I have tested these on native compiles with Ubuntu Linux 10.10 32-bit,