From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
To: cygwin@cygwin.com
Subject: Re: 1.7.14: Compiling GCC fails (Permission denied on mv)
Date: Thu, 12 Jul 2012 02:34:00 -0000 [thread overview]
Message-ID: <4FFE37C1.9080004@cs.utoronto.ca> (raw)
In-Reply-To: <4FFDE1DD.7080700@googlemail.com>
On 11/07/2012 4:28 PM, Thorolf Schulte wrote:
> okay, if Cygwin isn't able to perform 64-bit operations, then I can
> keep my old GCC, but just for curiosity I will try to compile it
> without multilib. I thought that it is 64-bit capable if one only
> compiles GCC on its own. Thank you for this information!
I missed that part... do you *need* it to run under cygwin? There's a
64-bit mingw cross-compiler cygwin package that can generate stand-alone
64-bit windows binaries..
Ryan
--
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
prev parent reply other threads:[~2012-07-12 2:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 12:41 Thorolf Schulte
2012-07-11 13:03 ` Csaba Raduly
2012-07-11 13:49 ` Thorolf Schulte
2012-07-11 19:59 ` Ryan Johnson
2012-07-11 20:28 ` Thorolf Schulte
2012-07-12 2:34 ` Ryan Johnson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FFE37C1.9080004@cs.utoronto.ca \
--to=ryan.johnson@cs.utoronto.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).