Re: [Mingw-users] [Mingw-w64-public] MinGW 64 on Windows Vista 64

[JonY <10walls@xxxxxxxxx>]

Sisyphus wrote:
> ----- Original Message ----- 
> From: "Danny Smith" <dannysmith@xxxxxxxxxxxx>
> .
> .
>>> -------------------------------------
>>> C:\_64\C>gcc -c try.c
>>> gcc: CreateProcess: No such file or directory
>>> -------------------------------------
>> This error message comes from pex_win32_exec_child in
>> libiberty/pex-win32.c.
>> I suspect that the process it is trying to create is cc1.exe.
>> I would not be surprised if the reason it can't find it is that
>> the _access() function on Vista64 has the same behaviour as  _access()
>> on Vista32.
>> Do the mingw-w64 headers have the __MINGW_ACCESS workaround?
>> See  PR 33281 in gcc's bugzilla for details.
>> Danny
> 
> Yes - I was wondering if that might be the cause, and it does seem to be the 
> trouble.
> If I add C:\_64\root-x86_64-pc-mingw32\libexec\gcc\x86_64-pc-mingw32\4.3.0 
> to the path (so that cc1.exe is locatable) then the error disappears, to be 
> replaced with:
> 
> ----------------------
> C:\_64\C>gcc -o try.exe try.c
> try.c:1:19: error: no include path in which to search for stdio.h
> try.c: In function 'main':
> try.c:4: warning: incompatible implicit declaration of built-in function 
> 'printf'
> ----------------------
> 
> This is the same error as occurs with the 32-bit version of gcc.exe (that 
> doesn't incorporate the __MINGW_ACCESS workaround) once the location of 
> cc1.exe has been added to the path.
> 
> Cheers,
> Rob 
> 
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> MinGW-users mailing list
> MinGW-users@xxxxxxxxxxxxxxxxxxxxx
> 
> You may change your MinGW Account Options or unsubscribe at:
> https://lists.sourceforge.net/lists/listinfo/mingw-users
> 

Hi,

GCC can't find the mingw64 headers. IMHO its the dreaded non-relocatable 
prefix, a rebuild may be needed.

Your first message indicated gcc is configured with 
"--prefix=/home/zhoujg/mingw/target".

gcc is probably searching $PREFIX/include for headers (and likely 
cc1.exe in $PREFIX as well), but not anywhere in C:\_64. I experienced 
the same problem when moving a gcc install from C:\MinGW to another drive.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
MinGW-users mailing list
MinGW-users@xxxxxxxxxxxxxxxxxxxxx

You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users