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

Previous Next

To reply to this bug, email your comments to 8550 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "Robert A. Lerche" <ral <at> msbit.com>
To: bug-libtool <at> gnu.org
Cc: gary <at> gnu.org
Subject: 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)]

Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Peter Rosin <peda <at> lysator.liu.se>
To: bug-libtool <at> gnu.org
Subject: Re: bug#8550: A libtool question (trying to compile with MS VC++
	from VS	2008 SP1)
Date: Tue, 26 Apr 2011 10:35:29 +0200

[Message part 1 (text/plain, inline)]

Hi Robert,

Den 2011-04-25 19:01 skrev Robert A. Lerche:
> 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.

I see one piece missing piece, and that is the archiver which isn't
autodetected by autotools (yet, a patch has been suggested, but it is
pending review, or something). The MS archiver (lib.exe) isn't anything like
a POSIX archiver (ar), so you need a wrapper for it. I suggest the ar-lib
wrapper included in Automake. However, there's no released version of
Automake that supplies it (yet), so I have attached it here for your
convenience.

I use it like this: .../configure AR="/path/to/ar-lib lib", but you may also
export AR if you like that better.

I think that should be it.

Cheers,
Peter

[ar-lib (text/plain, attachment)]

Message #11 received at 8550 <at> debbugs.gnu.org (full text, mbox):

From: Peter Rosin <peda <at> lysator.liu.se>
To: 8550 <at> debbugs.gnu.org
Cc: "Robert A. Lerche" <ral <at> msbit.com>
Subject: bug#8550: A libtool question (trying to compile with MS VC++ from
	VS 2008 SP1)
Date: Tue, 26 Apr 2011 21:10:49 +0200

[Message part 1 (text/plain, inline)]

[Forwarding this (sightly edited) to debbugs and Robert, the reporter]

Hi Robert,

Den 2011-04-25 19:01 skrev Robert A. Lerche:
> 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.

I see one missing piece, and that is the archiver, which isn't
autodetected by autotools (yet, a patch has been suggested, but it is
pending review, or something). The MS archiver (lib.exe) isn't anything like
a POSIX archiver (ar), so you need a wrapper for it. I suggest the ar-lib
wrapper included in Automake. However, there's no released version of
Automake that supplies it (yet), so I have attached it here for your
convenience.

I use it like this: .../configure AR="/path/to/ar-lib lib", but you may also
export AR if you like that better.

I think that should be it.

Cheers,
Peter

[ar-lib (text/plain, attachment)]

Message #14 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "Robert A. Lerche" <ral <at> msbit.com>
To: bug-libtool <at> gnu.org
Cc: Peter Rosin <peda <at> lysator.liu.se>
Subject: bug#8550 solved! [... compile with MS VC++ from VS 2008 SP1 ]
Date: Mon, 02 May 2011 12:07:33 -0700

My thanks to Peter Rosin.  The "ar-lib" script worked perfectly.

Not only did this allow me to compile libtool with MS Visual C++, in
turn it also solved another problem for me (a .dll incompatibility
that resulted in a crash in another module under Windows 7).

Open source proves its worth yet again.

Previous Next

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