From: Tim Prince <timothyprince@sbcglobal.net>
To: "Koide" <y-koide@h9.dion.ne.jp>, <cygwin@cygwin.com>
Subject: Re: Cygwin on Windows Me on Athlon64
Date: Sat, 27 Sep 2003 14:33:00 -0000 [thread overview]
Message-ID: <200309271405.h8RE5XjA150724@pimout3-ext.prodigy.net> (raw)
In-Reply-To: <000b01c38484$98929a80$0300a8c0@o8k4x4>
On Friday 26 September 2003 16:19, Koide wrote:
> Now I am using cygwin on Windows Me on AthlonXP .
>
> I will have Athlon64 system shortly . Then I want to use cygwin
> on Athlon64 . The executable files of programs comliled on Athlon64
> should be much faster than those are compiled on AthlonXP .
>
> Then now I am wondering if ;
> 1 . Can cygwin be installed correctly on Windows Me on Athlon64 .
> (Just the same as using the install wizard .)
You don't even know yet how ME will play on that box. If it does, cygwin
may work.
> 2 . To compile the program , gcc is certainly needed .
> To compile the program of 64bit , is it sufficient to install
> gcc using the install wizard and type "gcc ______.c" ?
Cygwin has no 64-bit support, ME has no 64-bit support. You could build a
cross compiler targeting your hardware, but it would be up to you to make it
work. First, you probably want to try out 32-bit software built with the
standard cygwin port of gcc, using the various architecture options, like
-march=athlon, -march=pentium4 -mfpmath=sse
--
Tim Prince
--
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/
prev parent reply other threads:[~2003-09-27 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 23:21 Koide
2003-09-26 23:25 ` Brian Dessent
2003-09-27 14:33 ` Tim Prince [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=200309271405.h8RE5XjA150724@pimout3-ext.prodigy.net \
--to=timothyprince@sbcglobal.net \
--cc=cygwin@cygwin.com \
--cc=tprince@computer.org \
--cc=y-koide@h9.dion.ne.jp \
/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).