Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
Message-Id: <4.3.1.2.20010731095116.0225fd48@pop.ma.ultranet.com>
X-Sender: lhall@pop.ma.ultranet.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Tue, 31 Jul 2001 09:53:03 -0400
To: Richard Cochran <cochran@cs.umass.edu>, <cygwin@cygwin.com>
From: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
Subject: Re: Problem linking to a MSVC DLL with gcc.
In-Reply-To: <Pine.OSF.4.31.0107310845330.25603-100000@freya.cs.umass.ed
 u>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 08:55 AM 7/31/2001, Richard Cochran wrote:
>Dear all,
>
>I find that linking to a third-party MSVC DLL works fine under NT4.0 using
>gcc 2.95.3-1, but linking under Win98 with gcc 2.95.3-4 fails. The linker
>cannot find exactly those symbols which would be provided by the DLL.
>
>How can I get this to work? Also, I've combed the list archives and the
>guide looking for FAQ or howtos on this subject. Can some one point me to
>a good guide?


Are you quite sure that the issue is not to be found somewhere in the 
different compiler versions you're running?  I think that would be the
best first step to tracking this down.  Unfortunately, I don't have any
other ideas. :-(



Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

