MIME-Version: 1.0
In-Reply-To: <30134265.post@talk.nabble.com>
References: <30132781.post@talk.nabble.com>	<20101104151639.GA12073@ednor.casa.cgf.cx>	<30134265.post@talk.nabble.com>
Date: Thu, 4 Nov 2010 18:22:08 +0000
Message-ID: <AANLkTikOPNKV9N74MB9-Oj3QPpfc6o-5k0O+n-F7mZib@mail.gmail.com>
Subject: Re: Cygwin paths in mingw64
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On 4 November 2010 17:22, LionAM wrote:
>
> Do I understand it right that the program would have to use the cygwin dlls
> - which, however, are 32bit. And it is not possible to run a 64bit-program
> using these dlls.

Correct. (I guess there will be a 64-bit Cygwin eventually, but there
are no plans for it at the moment.)

> The problem I have: I would like to build Atlas in Window - it works using
> the 32bit version with cygwin-gcc. However, I need the 64bit version as the
> total memory of my application is larger than the usable 2 GB.

Yep, sounds like a good use case for a hypothetical 64-bit Cygwin.

> Is there any alternative to cygwin to run the configure script and the make?

Yes, but they're obviously off-topic for this list. The mingw64
project may help with you that.

I think the list would be interested in hearing what problems exactly
you're having though. Your original message seemed to say that you had
successfully used Cygwin's mingw64-x86_64 toolchain to build your
program.

Andy

--
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