[prev in list] [next in list] [prev in thread] [next in thread] 

List:       otr-users
Subject:    Re: [OTR-users] libtool: undefined symbols not allowed
From:       Marcin Cieslak <saper () saper ! info>
Date:       2010-03-20 11:59:57
Message-ID: slrnhq9e5t.1685.saper () saper ! info
[Download RAW message or body]

Ian Goldberg <ian@cypherpunks.ca> wrote:
> On Fri, Mar 12, 2010 at 04:03:47PM +0000, Marcin Cieslak wrote:
> > C:\msys\1.0\bin\libtoolize: rerunning C:\msys\1.0\bin\libtoolize, to keep the \
> > correct libtool macros in-tree.
> 
> Hold on; are you running this *on* a Windows box?  Sorry; I hadn't fully
> understood that.  The instructions I gave were for using mingw as a
> cross-compiler from Linux (which is how we make the Windows binaries).

Yes, *on* a Windows box . Actually, that's the only problem with the build.
Having fixed that manually (by running libtool by hand) I was able
to build everything, including psi, psi-otr, qca with SSL and Windows GSSAPI
plugins, gcrypt, gpg-error, libotr and what-not.

Msys/Mingw combo basically give you environment that is posix enough
to run ./configure.

The next step would be to try compiling with Microsoft Visual C, not gcc,
if we aim at ultimate portability.

-- 
              << Marcin Cieslak // saper@saper.info >>


[prev in list] [next in list] [prev in thread] [next in thread]