public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Seyran Avanesyan" <seyran.avanesyan@tanner.com>
To: "NightStrike" <nightstrike@gmail.com>
Cc: <brian@dessent.net>, 	<gcc-help@gcc.gnu.org>
Subject: RE: 64-bit gcc
Date: Sat, 23 Aug 2008 02:13:00 -0000	[thread overview]
Message-ID: <D66102A43110FC488698F1C3B605E93108F962C1@exchange01.tanner.com> (raw)
In-Reply-To: <b609cb3b0808221859o7407c2danbb80ac0ed617724a@mail.gmail.com>

Thanks a lot.

> -----Original Message-----
> From: NightStrike [mailto:nightstrike@gmail.com]
> Sent: Friday, August 22, 2008 7:00 PM
> To: Seyran Avanesyan
> Cc: brian@dessent.net; gcc-help@gcc.gnu.org
> Subject: Re: 64-bit gcc
> 
> On 8/22/08, Seyran Avanesyan <seyran.avanesyan@tanner.com> wrote:
> > Thanks for reply.
> >
> > Yes, the target was Windows, and the separate fork is in active
> > development, this is why I was looking for earlier versions.
> > According to some posts gcc3.2.0 should do that. But it isn't, so I
> was
> > wondering if instead of downloading binaries I might have to compile
> > GCC/MinGW myself to get that working.
> 
> The mingw-w64 project that Brian linked you to can generate 32-bit as
> well as 64-bit binaries.  You can cross compile from 5 different
> systems, or you can compile natively.
> 
> The current version is stable enough to compile several
> high-visibility projects, including wxwidgets, vlc, ffmpeg, and more.
> If you need help with anything, post on the mailing list or forum for
> that project.

  reply	other threads:[~2008-08-23  2:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19 16:12 Restricting symbol binding within shared object Arindam
2008-08-19 16:58 ` special comments handling in the C compiler Tim Wang
2008-08-22  1:52   ` extern "C" From command line Seyran Avanesyan
2008-08-22  2:12     ` Brian Dessent
2008-08-23  1:38       ` Seyran Avanesyan
2008-08-23  2:37         ` Brian Dessent
2008-08-23  2:46           ` Seyran Avanesyan
2008-08-22  2:04   ` 64-bit gcc Seyran Avanesyan
2008-08-22 11:01     ` Brian Dessent
2008-08-22 20:09       ` Seyran Avanesyan
2008-08-22 22:32         ` Brian Dessent
2008-08-22 22:45           ` Seyran Avanesyan
2008-08-23  2:31             ` Brian Dessent
2008-08-23  2:45               ` NightStrike
2008-08-23  2:49               ` Seyran Avanesyan
2008-08-23  3:18                 ` Brian Dessent
2008-08-23  2:00         ` NightStrike
2008-08-23  2:13           ` Seyran Avanesyan [this message]
2008-08-19 18:49 ` Restricting symbol binding within shared object Ian Lance Taylor
2008-08-20 19:36   ` Arindam
2008-08-21  4:43     ` Ian Lance Taylor

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=D66102A43110FC488698F1C3B605E93108F962C1@exchange01.tanner.com \
    --to=seyran.avanesyan@tanner.com \
    --cc=brian@dessent.net \
    --cc=gcc-help@gcc.gnu.org \
    --cc=nightstrike@gmail.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).