missing link.exe

[gweather]

Windows 10 PRO 64BIT
CODE BLOCKS 16.01 (just downloaded from sourceforge.net codeblocks-16.01-mingw-setup.exe

created a c project and tried building the default code.

BUILD LOG:

-------------- Build: Debug in HelloWorld (compiler: GNU GCC Compiler)---------------

gcc.exe -Wall -g  -c C:\Work\HelloWorld\main.c -o obj\Debug\main.o
link.exe  -o bin\Debug\HelloWorld.exe obj\Debug\main.o   
Execution of 'link.exe  -o bin\Debug\HelloWorld.exe obj\Debug\main.o' in 'C:\Work\HelloWorld' failed.

TOOLCHAIN POINTS TO C:\Program Files (x86)\CodeBlocks\MinGW\bin

No link.exe file there and after a search of c: no link.exe found at all

Is this file missing or is another file used in its place?

[stahta01]

I know of no time that GCC used an link.exe.

For DLL/Shared/normal linking gcc.exe or g++.exe is normally used in CB.
For Static library, I think ar.exe is use; but, I am not sure of that.

Tim S.

[gweather]

I printed out the build log.  That is the only thing I have to go on and it says link.exe failed.  I am not sure what else to look for.

[stahta01]

What commands are used in the toolchain settings?

Please post the build log!

Tim S.

[stahta01]

http://wiki.codeblocks.org/index.php/FAQ-Compiling_(errors)#Q:_How_do_I_troubleshoot_a_compiler_problem.3F

[gweather]

The full build log is in the original message.  Here it is again:


-------------- Build: Debug in HelloWorld (compiler: GNU GCC Compiler)---------------

gcc.exe -Wall -g  -c C:\Work\HelloWorld\main.c -o obj\Debug\main.o
link.exe  -o bin\Debug\HelloWorld.exe obj\Debug\main.o   
Execution of 'link.exe  -o bin\Debug\HelloWorld.exe obj\Debug\main.o' in 'C:\Work\HelloWorld' failed.

[stahta01]

What commands are used in the toolchain settings?

[gweather]

C compiler: gcc.exe
C++ compiler: g++.exe
Linker for dynamic libs: link.exe
linker for static libs: ar.exe
Debugger: GDB/CDB debugger:Default
Resource compiler: windres.exe
Make program: make.exe

The compiler's installation directory: C:\Program Files (x86)\CodeBlocks\MinGW

[stahta01]

C compiler: gcc.exe
C++ compiler: g++.exe
Linker for dynamic libs: link.exe
linker for static libs: ar.exe
Debugger: GDB/CDB debugger:Default
Resource compiler: windres.exe
Make program: make.exe

The compiler's installation directory: C:\Program Files (x86)\CodeBlocks\MinGW

Fix this "Linker for dynamic libs: link.exe" as I stated in my first post!

Edit: If you plan to use C++, change "link.exe" to "g++.exe"

Tim S.

[gweather]

What do I replace link.exe with.  I can find nothing about what it should be.

[stahta01]

For DLL/Shared/normal linking gcc.exe or g++.exe is normally used in CB.

The normal value is g++.exe
If you plan to never use C++, some people use gcc.exe.

Tim S.

[gweather]

I was writing the code in c not c++.  I used the default settings and got the error.  The ar.exe links static libraries according to the toolchain menu.  Is there an issue with the defaults for CB?  Is there an explanation about the problem that I missed?

[stahta01]

I was writing the code in c not c++.  I used the default settings and got the error.  The ar.exe links static libraries according to the toolchain menu.  Is there an issue with the defaults for CB?  Is there an explanation about the problem that I missed?

FIX THE LINKER IN THE TOOLCHAIN SETTING!!!!!!!!!!

You changed the value; the default was never link.exe till you changed it!!!

Tim S.

[gweather]

These are the default values.  I did not change anything after the install.  I ran  codeblocks-16.01mingw-setup.exe that I downloaded from sourceforge.net from the Code Blocks web download link and then created a console app and used the defaults.  Again, I did not change anything and clicked the build icon and it gave the posted error.

What is suppose to be there?

[stahta01]

I was writing the code in c not c++.

I used the default settings and got the error.

No you used what someone set the values to on your computer; not the default settings

The ar.exe links static libraries according to the toolchain menu.

Correct.
But, the Shared/DLL linker is used for linking everything that is not an static library!

Is there an issue with the defaults for CB?

No, the issue is user error and the fact that CB setting can only be manually deleted; so, they stay during an uninstall/install cycle.

Is there an explanation about the problem that I missed?

See the above answer.

Tim S.