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:	<00ff01c089fa$51865000$275c100a@actfs.co.uk>
From:	"Malcolm Boekhoff" <Malcolm DOT Boekhoff AT actfs DOT co DOT uk>
To:	"Cygwin News Group" <cygwin AT sources DOT redhat 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:	Mon, 29 Jan 2001 13:49:36 -0000

The way to solve "internal compiler error" messages, is to binary chop the source file and recompile. Eventually you will locate the
line causing the error.

----- Original Message -----
From: "Leo Liberti" <leoliberti AT yahoo DOT com>
To: <cygwin AT cygwin DOT com>
Sent: Friday, January 26, 2001 5: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 -