public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: NightStrike <nightstrike@gmail.com>
To: Sisyphus <sisyphus1@optusnet.com.au>
Cc: "Tim Prince" <tprince@myrealbox.com>,
	"Rodolfo Lima" <rodolfo@rodsoft.org>,
	 	gcc-help@gcc.gnu.org
Subject: Re: gcc for windows
Date: Sun, 30 Mar 2008 13:31:00 -0000	[thread overview]
Message-ID: <b609cb3b0803300631v57e7f6c9q92dbad5d256055fa@mail.gmail.com> (raw)
In-Reply-To: <EDE86BF8EA9C4EA586B89CCB8D9D7710@desktop2>

On 3/30/08, Sisyphus <sisyphus1@optusnet.com.au> wrote:
>
> ----- Original Message -----
> From: "Tim Prince" <tprince@myrealbox.com>
> .
> .
> > The following URL has the most up to date pre-built gnu C and Fortran,
> > including 64-bit mingw with support libraries (but no C++):
> > http://gcc.gnu.org/wiki/GFortranBinaries
>
> Unfortunately (for me, anyway) the 64-bit mingw that's available there
> doesn't work with Vista. It suffers from the well known access() problem on
> Vista. I find it extremely frustrating that there's still no 64-bit gcc
> compiler available for Vista 64 users ... but no-one else seems to give a
> shit.

I know a few people that care, myself included.  Go here:

http://mingw-w64.sf.net/

The natively hosted gfortran still doesn't work, however, and
segfaults on Hello, World (This is not the access() issue... that
issue doesn't exist anymore).  You have to cross compile it.  If you'd
like to help fix it, there's a bug open that I wrote for the issue:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35159

There is a company aclled "EquationWorld" or something like that that
figured out how to get a working gfortran compiler, but I'm not quite
sure how they did it.  I think they did a combination of things,
including shutting off all optimization.


> C:\_64\C>type try.c
> #include <stdio.h>
> int main() {
>    printf("hello world\n");
>    return 0;
> }
>
> C:\_64\C>x86_64-pc-mingw32-gcc -o try.exe try.c
> x86_64-pc-mingw32-gcc: CreateProcess: No such file or directory

This issue was fixed so that access() is always properly handled.

  reply	other threads:[~2008-03-30 13:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-23 18:47 Freeman Gilmore
2008-03-23 19:06 ` Rodolfo Lima
2008-03-23 21:06   ` Tim Prince
2008-03-30 10:20     ` Sisyphus
2008-03-30 13:31       ` NightStrike [this message]
2008-03-31  7:25         ` Sisyphus
2008-03-31 10:17           ` Sisyphus
  -- strict thread matches above, loose matches on Subject: below --
2022-12-17  8:10 GCC for Windows Oleksii Khramkov
2022-12-17  9:07 ` i.nixman
     [not found]   ` <CAHe=5EB4KPGLFuYkZrB0ur-FbHAFm0z85qrvQe+gkc+sH=q40g@mail.gmail.com>
2022-12-21  7:42     ` i.nixman
2022-12-21  7:55       ` Jonathan Wakely
2000-03-30 13:00 Owlex224
2000-03-30 15:46 ` Alexandre Oliva
2000-04-01  0:00   ` Alexandre Oliva
2000-03-30 21:27 ` Curtis R. Anderson
2000-04-01  0:00   ` Curtis R. Anderson
2000-04-01  0:00 ` Owlex224

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=b609cb3b0803300631v57e7f6c9q92dbad5d256055fa@mail.gmail.com \
    --to=nightstrike@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=rodolfo@rodsoft.org \
    --cc=sisyphus1@optusnet.com.au \
    --cc=tprince@myrealbox.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).