GNU bug report logs - #8550
A libtool question (trying to compile with MS VC++ from VS 2008 SP1)

Previous Next

Package: libtool;

Reported by: "Robert A. Lerche" <ral <at> msbit.com>

Date: Mon, 25 Apr 2011 17:14:02 UTC

Severity: normal

Full log


View this message in rfc822 format

From: "Robert A. Lerche" <ral <at> msbit.com>
To: 8550 <at> debbugs.gnu.org
Cc: gary <at> gnu.org
Subject: bug#8550: A libtool question (trying to compile with MS VC++ from VS 2008 SP1)
Date: Mon, 25 Apr 2011 10:01:33 -0700
[Message part 1 (text/plain, inline)]
Hi.

I am a consultant working for a large client on a high-profile
security-related project.

[trying to build libtool-2.4 with MSVC++]

I'm trying to introduce use of open source software instead of
proprietary systems.  The particular project uses Python for the
client, with OpenSSL for secure communications and a dynamic engine to
talk to a hardware security device.

This lash-up requires engine_pkcs11 and libp11, so in turn I need
libtool.

I have been able to compile everything with "pure Microsoft" tools
*except* libtool.

During development, as a workaround, I'm using MinGW/MSYS.  This
works.  However, I'd like to eliminate that dependency (various .dll
files) if possible.

I've seen tantalizing hints of MS VC++ support in a couple of posts on
Savannah but when I try to build libtool with the MS compiler I'm
getting stuck.  I have set up a PATH that includes MSYS for the tools
but omits gcc.  This almost works.

I attach a log of the current spot where my build fails.  

Thanks for any help you can give me.
[build-libtool-2.4-log (application/octet-stream, inline)]

This bug report was last modified 14 years and 108 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.