Building OpenConnect with libintl

2012-11-08 Thread Woodhouse, David
I saw the OpenBSD 5.2 release and figured I should make sure the OpenConnect VPN client builds OK on it still. It does, but I noticed that it didn't build with localisation support, and tried to fix that. It seems that libintl *is* present, but it's installed in /usr/local and the compiler doesn't

Re: Building OpenConnect with libintl

2012-11-08 Thread Woodhouse, David
On Thu, 2012-11-08 at 14:36 +0100, Marc Espie wrote: > Pass LIBTOOL=/usr/bin/libtool on make's command line. Thanks, that works. This commit should make it work for everyone automatically, without them having to override it manually: http://git.infradead.org/users/dwmw2/openconnect.git/commitdiff/

Re: Building OpenConnect with libintl

2012-11-08 Thread Woodhouse, David
On Thu, 2012-11-08 at 14:36 +0100, Marc Espie wrote: > > Pass LIBTOOL=/usr/bin/libtool on make's command line. > > Trying to get through the spaghetti of gnu autocrap only leads to > insanity. > > That falls under the "don't fight that shit, it's hopeless". Hm, OpenBSD libtool doesn't seem to hono

Re: Building OpenConnect with libintl

2012-11-09 Thread Woodhouse, David
On Fri, 2012-11-09 at 11:17 +0100, Marc Espie wrote: > On Thu, Nov 08, 2012 at 03:38:18PM +0000, Woodhouse, David wrote: > > On Thu, 2012-11-08 at 14:36 +0100, Marc Espie wrote: > > > > > > Pass LIBTOOL=/usr/bin/libtool on make's command line. > > > > &g

Re: Building OpenConnect with libintl

2012-11-13 Thread Woodhouse, David
On Fri, 2012-11-09 at 12:19 +0100, Marc Espie wrote: > > autocrap is part of the problem, not the solution. Their documentation > concerning version numbering, and all the fuzz they add around it don't > help at all. The "old" style (major.minor) is fairly simple to understand > and to use, actuall