From: vischne AT ibm DOT net
Subject: Re: problem with EGCS on gun-win32 b18!! HELP
14 Dec 1997 22:33:59 -0800
Message-ID: <199712150552.FAA53122.cygnus.gnu-win32@out5.ibm.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
To: gnu-win32 AT cygnus DOT com DOT Mumit DOT Khan DOT Fri (khan AT xraylith DOT wisc DOT edu),
        "12.Dec.1997.19":30:36 DOT -0600 AT out5 DOT ibm DOT net

root  writes:
> Hi!
>       When I compile a C++ code with egcs (over gnuwin32 b18) on win95, I get
> no errors. (the
> code works fine on my linux box). But when I run the executable, I get
> an error
> message telling me that I miss the "abort.dll" file. What the hell could
> this be due to?
Dumping egcs right over gnu-win32 b18 is probably idea, given that others
seem to be having trouble as well. One thing to watch out for is that you
CANNOT use import libraries (eg., kernel32.a or libcygwin32.a) that were
created with b18 tools. You must use the egcs supplied ones.

That's interesting.  The first version of ming were compatible with kernel32.
I wonder why it is necessary to have two separate setups, one cygwin and one
mingw32, when the cygwin ./configure and make capabilities are so much better
at this time.  It seems to make more sense to have ming as an auxiliary system,
and use the cygwin tools to run ming.


-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".