Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <3989DC29.5AEE48C3@ece.gatech.edu>
Date: Thu, 03 Aug 2000 16:55:05 -0400
From: Charles Wilson <cwilson@ece.gatech.edu>
MIME-Version: 1.0
To: cockerham@flame.org
CC: cygwin@sourceware.cygnus.com
Subject: Re: Linking static library from Mingw32 with Visual C++
References: <20000803195616.25026.qmail@kechara.flame.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

cockerham@flame.org wrote:
> 
> I compiled a static library using the -mno-cygwin option on gcc.
> I need to link that library into an executable using Visual C++.

Erm. cygwin's "gcc -mno-cygwin" != mingw's "gcc"

> 
> When I try, I get this:
> 
> error LNK2001: unresolved external symbol ___udivdi3
> also, ___imp__iob, ___umoddi3, and _main!
> 
> I searched through the libraries in VC++, they don't contain any of
> these, except _main of course.
> 
> So, I guess what I need is to have Mingw32 not put these in the
> library.  But, what are they and where do they come from?

I don't think you can a statlib created by cygwin's gcc -mno-cygwin
using MSVC. Perhaps mingw can create MSVC-compatible libs, but I doubt
it.

--Chuck

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com