Author Topic: linking failed. i really have no idea.  (Read 4497 times)

Offline dustcool

  • Single posting newcomer
  • *
  • Posts: 2
linking failed. i really have no idea.
« on: September 25, 2010, 06:34:13 pm »
i have no idea about this:

when i click 【rebuild】 button,something happened in the 【build log】 TAB as  followed :

-------------- Clean: Debug in WINDOWS_VM ---------------

Cleaned "WINDOWS_VM - Debug"

-------------- Build: Debug in WINDOWS_VM ---------------

bitwise.c
cmdline.c
dbgcmd.c
debug.c
exenv.c
init.c
initwin32.c
interupt.c
log.c
main.c
reformat.c
run.c
win32.c
Linking console executable: E:\WorkingSpace\VM\Output\WINDOWS_VM.exe
Nothing to be done.


// *******************************************************
this is a console application project, i get all the obj files after 【rebuild】, but WINDOWS_VM.exe missed.======>compile passed, linking failed.

could anybody fix it?
tks!!

Offline stahta01

  • Lives here!
  • ****
  • Posts: 7785
    • My Best Post
Re: linking failed. i really have no idea.
« Reply #1 on: September 25, 2010, 07:17:16 pm »
Turn on "Full Compiler Logging"

http://wiki.codeblocks.org/index.php?title=FAQ#Q:_How_do_I_troubleshoot_an_compiler_problem.3F

Tim S.
PS: I am going offline for most of day; so not going to help you anymore.
C Programmer working to learn more about C++ and Git.
On Windows 10 64 bit and Windows 11 64 bit.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline dustcool

  • Single posting newcomer
  • *
  • Posts: 2
Re: linking failed. i really have no idea.
« Reply #2 on: September 27, 2010, 06:08:50 pm »
Turn on "Full Compiler Logging"

http://wiki.codeblocks.org/index.php?title=FAQ#Q:_How_do_I_troubleshoot_an_compiler_problem.3F

Tim S.
PS: I am going offline for most of day; so not going to help you anymore.

OK, I Turned on "Full Compiler Logging".
and got info as followed:

-------------- Clean: Release in WINDOWS_VM ---------------

Cleaned "WINDOWS_VM - Release"

-------------- Build: Release in WINDOWS_VM ---------------

CL.EXE /nologo     /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\MFC\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\ATL\Include"  /c bitwise.c /FoE:\WorkingSpace\VM\Output\bitwise.obj
bitwise.c
CL.EXE /nologo     /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\MFC\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\ATL\Include"  /c cmdline.c /FoE:\WorkingSpace\VM\Output\cmdline.obj
cmdline.c
CL.EXE /nologo     /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\MFC\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\ATL\Include"  /c dbgcmd.c /FoE:\WorkingSpace\VM\Output\dbgcmd.obj
dbgcmd.c
CL.EXE /nologo     /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\MFC\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\ATL\Include"  /c debug.c /FoE:\WorkingSpace\VM\Output\debug.obj
debug.c
CL.EXE /nologo     /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\MFC\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\ATL\Include"  /c exenv.c /FoE:\WorkingSpace\VM\Output\exenv.obj
exenv.c
CL.EXE /nologo     /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\MFC\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\ATL\Include"  /c initwin32.c /FoE:\WorkingSpace\VM\Output\initwin32.obj
initwin32.c
CL.EXE /nologo     /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\MFC\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\ATL\Include"  /c interupt.c /FoE:\WorkingSpace\VM\Output\interupt.obj
interupt.c
CL.EXE /nologo     /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\MFC\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\ATL\Include"  /c log.c /FoE:\WorkingSpace\VM\Output\log.obj
log.c
CL.EXE /nologo     /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\MFC\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\ATL\Include"  /c main.c /FoE:\WorkingSpace\VM\Output\main.obj
main.c
CL.EXE /nologo     /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\MFC\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\ATL\Include"  /c reformat.c /FoE:\WorkingSpace\VM\Output\reformat.obj
reformat.c
CL.EXE /nologo     /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\MFC\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\ATL\Include"  /c run.c /FoE:\WorkingSpace\VM\Output\run.obj
run.c
CL.EXE /nologo     /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\MFC\Include" /I"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\ATL\Include"  /c win32.c /FoE:\WorkingSpace\VM\Output\win32.obj
win32.c
LINK.EXE /nologo /LIBPATH:"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\Lib" /LIBPATH:"D:\Softwares\Developing Tools\Microsoft Visual Studio\VC98\MFC\Lib"  /out:E:\WorkingSpace\VM\Output\WINDOWS_VM.exe  E:\WorkingSpace\VM\Output\bitwise.obj E:\WorkingSpace\VM\Output\cmdline.obj E:\WorkingSpace\VM\Output\dbgcmd.obj E:\WorkingSpace\VM\Output\debug.obj E:\WorkingSpace\VM\Output\exenv.obj E:\WorkingSpace\VM\Output\initwin32.obj E:\WorkingSpace\VM\Output\interupt.obj E:\WorkingSpace\VM\Output\log.obj E:\WorkingSpace\VM\Output\main.obj E:\WorkingSpace\VM\Output\reformat.obj E:\WorkingSpace\VM\Output\run.obj E:\WorkingSpace\VM\Output\win32.obj   
Done.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
as before, got obj , exe missed.

waiting for your help~
tks!!

Offline stahta01

  • Lives here!
  • ****
  • Posts: 7785
    • My Best Post
Re: linking failed. i really have no idea.
« Reply #3 on: September 27, 2010, 08:41:41 pm »
Open up MS Visual Studio Cmd Window and try the linking command and see if it returns an error.

What Windows OS are you running?
What version of Visual C++?
Are they compatible?

What version of Code::Blocks?

Note: I have no idea of how old of the MS Visual Studio versions can be used with Code::Block 10.05 and 8.02.

Tim S.
« Last Edit: September 27, 2010, 08:48:21 pm by stahta01 »
C Programmer working to learn more about C++ and Git.
On Windows 10 64 bit and Windows 11 64 bit.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 13406
    • Travis build status
Re: linking failed. i really have no idea.
« Reply #4 on: September 28, 2010, 08:34:31 am »
The output looks like VC6...

Here is a link about it:
http://wiki.codeblocks.org/index.php?title=FAQ#Q:_Is_it_possible_to_use_Visual_C.2B.2B_6.0_with_Code::Blocks.3F

I've use 2003 and 2008 with C::B
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]