Win10 64 bit, Dev-C++ 5.11, recipe for target ‘main.o’ failed

[xiaolaba]

can somebody help with this topic or see same issue

win10, 64bits

the test code,

#include <iostream>

/* run this program using the console pauser or add your own getch, system("pause") or input loop */

int main(int argc, char** argv) {
    return 0;
}

.
.
.
.
.
.

the error log

Compiling project changes...
--------
- Project Filename: C:\myProject\Project6.dev
- Compiler Name: TDM-GCC 4.9.2 64-bit Release

Building makefile...
--------
- Filename: C:\myProject\Makefile.win

Processing makefile...
--------
- Makefile Processor: C:\Program Files (x86)\Dev-Cpp\MinGW64\bin\mingw32-make.exe
- Command: mingw32-make.exe -f "C:\myProject\Makefile.win" all

g++.exe -c main.cpp -o main.o -I"C:/Program Files (x86)/Dev-Cpp/MinGW64/include" -I"C:/Program Files (x86)/Dev-Cpp/MinGW64/x86_64-w64-mingw32/include" -I"C:/Program Files (x86)/Dev-Cpp/MinGW64/lib/gcc/x86_64-w64-mingw32/4.9.2/include" -I"C:/Program Files (x86)/Dev-Cpp/MinGW64/lib/gcc/x86_64-w64-mingw32/4.9.2/include/c++" 

C:\myProject\Makefile.win:28: recipe for target 'main.o' failed

mingw32-make.exe: *** [main.o] Error -1073741502

Compilation results...
--------
- Errors: 0
- Warnings: 0
- Compilation Time: 52.22s

[Daniel Mylle]

exactly the same error here... anyone a solution??

danny

[Bobsien]

I have the same problem ... But, I has reinstalled the software and i installed the Windows Resource Called "Windows subsystem for Linux", and a second error occur.
The IDE does not locate the directory lib32 into MinGW64 dir. I was copyed this directory from "x86_64-w64-mingw32", and the compilation has sucessfull one time (some one time).

I believe this problem is related to Windows SFC or Antivirus / Defender, but i have disabled my AV and the problem persist.

[Edwin Khundi]

Uninstall the version of dev c++ that  is causing  compilatio/builde  errors ...and thereafter install the portable versionw  which  be downloaded from https://sourceforge.net/projects/orwelldevcpp/ ...I had the same problem and it was fixed after installing the portable version.