From: "Sisyphus" <sisyphus1@optusnet.com.au>
To: "NightStrike" <nightstrike@gmail.com>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: gcc for windows
Date: Mon, 31 Mar 2008 07:25:00 -0000 [thread overview]
Message-ID: <6CC8005619174DB7AAD6125D19B0DECF@desktop2> (raw)
In-Reply-To: <b609cb3b0803300631v57e7f6c9q92dbad5d256055fa@mail.gmail.com>
----- Original Message -----
.
.
>> 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.
I removed my existing installations of mingw64 (none of which worked,
anyway). And I downloaded mingw-w64-bin-x86_64-mingw_20080320.tar.bz2 from
http://sourceforge.net/project/showfiles.php?group_id=202880&package_id=245516&release_id=546049 .
I'm on an AMD64 box - I think that was binary I was supposed to grab.
(Please let me know if I've gone off and found the wrong file.)
I unpacked that tarball to C:\_64\mingw64 and prepended C:\_64\mingw64\bin
to my path. The following looks right to me:
------------------------------------
C:\_64\C>gcc -v
Using built-in specs.
Target: x86_64-pc-mingw32
Configured with:
../gcc/configure --target=x86_64-pc-mingw32 --prefix=/tmp/win64
root --with-sysroot=/tmp/win64root --host=x86_64-pc-mingw32 --disable-nls --with
-gmp=/tmp/mathwin64 --with-mpfr=/tmp/mathwin64
Thread model: win32
gcc version 4.4.0 20080320 (experimental) (GCC)
------------------------------------
Unfortunately, trying to build my 'hello' program still fails in exactly the
same way as before.
------------------------------------
C:\_64\C>gcc -o try.exe try.c
gcc: CreateProcess: No such file or directory
------------------------------------
If that's not the access() problem, then it must be something else :-)
I'll try googling that error and chasing it down - though I'm anticipating
it will be a wild goose chase.
Any advice on things to try will be gratefully accepted.
Thanks for the link, NightStrike - it was worth a shot. (And, I might even
have some success, yet, if I persevere.)
Cheers,
Rob
next prev parent reply other threads:[~2008-03-31 7:25 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
2008-03-31 7:25 ` Sisyphus [this message]
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=6CC8005619174DB7AAD6125D19B0DECF@desktop2 \
--to=sisyphus1@optusnet.com.au \
--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).