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: <20000720094222.78726.qmail@hotmail.com>
X-Originating-IP: [203.97.2.246]
From: "Danny Smith" <danny_r_smith AT hotmail DOT com>
To: <cygwin AT sources DOT redhat DOT com>
Subject: Re: binutils prerelease available for testing (feedback needed)
Date: Thu, 20 Jul 2000 21:40:37 +1200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600

Hi
You may be ahead of me on this but...
I have experienced similar problems as report by Eric Fifer and Charles
Wilson using binutils-000718, with access violations linking against C
dlls with data exports or with C++ dlls.

But, rebuilding binutils-000718 after reverting the changes made to
gas/config/obj_coff.c
(http://sources.redhat.com/ml/binutils/2000-07/msg00226.html)  back to
binutils-000717 version, I can successfully build and link against dlls,
using either dllwrap or gcc -shared.  This works also with -mno-cygwin.
I have tested linking against implib as well as directly aginst dll
without implib.  Both work, for C and C++, and dll data is exported
correctly.   Also with standalone MingW.

Hope this helps.

Regards


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com