X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-1.0 required=5.0	tests=AWL,BAYES_00,T_RP_MATCHES_RCVD
X-Spam-Check-By: sourceware.org
Message-ID: <4DA46E3E.8060004@cs.umass.edu>
Date: Tue, 12 Apr 2011 11:22:38 -0400
From: Eliot Moss <moss@cs.umass.edu>
Reply-To: moss@cs.umass.edu
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: 64bit (g)fortran JNI
References: <io1o4k$euu$1@dough.gmane.org> <BANLkTikh=3DLDE7s-yVOYo=CZ6u9GNvfXw@mail.gmail.com> <4DA46998.5050008@cs.umass.edu> <io1q1k$shi$1@dough.gmane.org>
In-Reply-To: <io1q1k$shi$1@dough.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On 4/12/2011 11:10 AM, Hans Horn wrote:
> On 4/12/2011 8:02 AM, Eliot Moss wrote:
>>> For x64 Windows releated target questions it would be better if you
>>> are posting to mingw-w64's ML: I redirect this thread to this list.

> Elliot,     [Eliot]
>
> I've been using the cygwin gcc compiler (with the -mno-cygwin option) for years to build JNI dlls
> (interfacing with C code) that ran fine under 32bit JVMs on windows32.
>
> After migrating to 64bit windows7 last year, I've been using x86_64-w64-mingw32-gcc to do the same,
> ie. build JNI dlls that run fine under 64bit JVMs on windows64.
>
> However, throwing fortran in the mix is causing the trouble I'm seeking help for.

I see; I appreciate knowing that. Of course, though you're using
cygwin to run the compiler, it's really a cross compile to the
Windows environment, not *targeting* cygwin.  But I can see why
it might be at least a little relevant to this list.  Sorry -- EM

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

