Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Mon, 5 Apr 2004 10:46:47 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Loading gcc-compiled DLL with Java (JNI) crashes when using newer (>1.5.5) cygwin1.dll Message-ID: <20040405144647.GA15144@coc.bosbc.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <404E3A33 DOT 4090805 AT Proefrock DOT de> <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040310164105 DOT 03a223e0 AT 127 DOT 0 DOT 0 DOT 1> <20040403164526 DOT GB6264 AT coc DOT bosbc DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Sun, Apr 04, 2004 at 01:44:56PM -0700, Hans Horn wrote: >>>The correct switch is -mno-cygwin. -mno-cygwin should be equivalent to >>>building with the mingw compiler unless you try to include cygwin header >>>files or libraries, which is a common mistake. > >Chris, sorry that was I typo in my posting! >I used gcc -mno-cygwin rather than -no-cygwin, and this did NOT produce a >working dll!!!! >mingw-gcc did! Well, there's really not enough data to go on here. I assume that you must have linked cygwin libraries in somehow. -- Christopher Faylor Cygwin Co-Project Leader TimeSys, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/