Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<008c01c087cc$693541f0$6701a8c0@dafcor1qondarn>
From:	"David Feustel" <dfeustel AT mindspring DOT com>
To:	"Leo Liberti" <leoliberti AT yahoo DOT com>, <cygwin AT cygwin DOT com>
References:	<20010126173102 DOT 3803 DOT qmail AT web1902 DOT mail DOT yahoo DOT com>
Subject:	Re: Using cygwin to make C++ DLL's to link with MSVC++
Date:	Fri, 26 Jan 2001 14:15:57 -0500
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2919.6700

Is there any way you could try compiling the code
using Intel's C++ compiler?

----- Original Message ----- 
From: "Leo Liberti" <leoliberti AT yahoo DOT com>
To: <cygwin AT cygwin DOT com>
Sent: Friday, January 26, 2001 12:31 PM
Subject: RE: Using cygwin to make C++ DLL's to link with MSVC++


> Thanks to everyone who lent a hand.
> 
> Just to summarize what the situation is (for
> future reference in case somebody asks something
> similar):
> 
> 1) I had software written in C++ and tested (and
> working) with GNU c++ compiler
> 2) It wouldn't compile with MS VC++ 6.0 because
> of an INTERNAL COMPILER ERROR (probably a bug
> in the microsoft compiler).
> 
> Solutions:
> 1) compile and link DLLs with CygWin32:
> not a viable solution because of mangling
> C++ name schemes incompatibility between
> microsoft and everyone else's binary object
> formats
> 2) compile and link DLLs with UWin:
> not a viable solution because it implicitely
> calls CL.EXE (microsoft C++ compiler
> command line executable) which of course
> fails with its internal bug.
> 3) external solutions, like mks: 
> not tested because
> it seems to me that they actually integrate
> a unix-like environment with CL.EXE, 
> substantially similar to solution 2, already
> failed
> 4) follow CL.EXE error message and contact M$
> technical
> service
> not possible because the website for technical
> support actually consists of a list of prices:
> do we have to pay M$ to tell them their
> software have bugs?
> 
> Final recommendation:
> 
> Dump CL.EXE, dump the whole OS, forget
> it ever existed and go on developing in
> more reasonable environments.
> 
> Again, thanks for your help.
> 
> Leo
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Auctions - Buy the things you want at great prices. 
> http://auctions.yahoo.com/
> 
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple
> 


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -