Link error after converting from 6.0 to 2005

  • Thread starter Thread starter Michael Tissington
  • Start date Start date
M

Michael Tissington

After converting from 6.0 to 2005 when I try to Compile my project I'm
getting a LINK error

Error 1 fatal error LNK1181: cannot open input file " ?/.obj"

Any ideas how to fx this please ?
 
Hi Michael,
After converting from 6.0 to 2005 when I try to Compile
my project I'm getting a LINK error

Error 1 fatal error LNK1181: cannot open input file " ?/.obj"
Click to expand...

Based on the error message, it appears the VC2005 linker could not find the
target input file due to a corrupted input file path name. So would you
have any custom linker's input file setting in your upgraded project?

By the way, I also did a simple test on my local machine, but unable to
repro this problem with a wizard generated MFC6 MDI application. I think
If you can upload a small self-alone repro sample project (zipped) to us,
we may perform some research on it directly.(Please remove the "online" of
my email alias).


Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Gary,

The project is BIG and the error only occured on this project ... I'm
wondering if there is some sort of corruption in one of the project files
(not the source file) ... which file containes that path names ? what about
sending you just the sln or other file ?

--
Michael Tissington
http://www.oaklodge.com
http://www.tabtag.com

"Gary Chang[MSFT]" said:
Hi Michael,
After converting from 6.0 to 2005 when I try to Compile
my project I'm getting a LINK error

Error 1 fatal error LNK1181: cannot open input file " ?/.obj"
Click to expand...

Based on the error message, it appears the VC2005 linker could not find
the
target input file due to a corrupted input file path name. So would you
have any custom linker's input file setting in your upgraded project?

By the way, I also did a simple test on my local machine, but unable to
repro this problem with a wizard generated MFC6 MDI application. I think
If you can upload a small self-alone repro sample project (zipped) to us,
we may perform some research on it directly.(Please remove the "online" of
my email alias).


Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no
rights.
Click to expand...
 
Hi Michael,

I suggest you can check your upgraded project's property page, one location
is the Configuration Properties\C/C++\Output Files\Object File Name, for an
upgraded VC6 project, it might be as ".\Debug/".

By the way, the genuine VC2005 project directory's location is different
from the VC6 and VS2003, --unlike the VS2003, whose default project
directory is also its solution's directory, in VS2005 the project has its
own directory under the solution's directory:

in VC6
\Demo1: Demo1.dsw, Demo1.dsp,Demo1.cpp,Demo1.h...

in VS2003
\Demo1: Demo1.sln, Demo1.vcproj,Demo1.cpp,Demo1.h...

in VS2005:
\Demo2: Demo2.sln, ... Demo2(Dir)...
\Demo2\Demo2\: Demo2.vcproj,Demo2.cpp,Demo2.h...


Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.
 
OK, I think the problem is that my C++ directories or PATH settings have got
messed up because its finding the compiler for C++ 6.0 instead of VS 2005.

How do I fix this ?
 
Hi Michael,

VS2005 will not use the VC6's debugger, so I don't think this causes the
problem.

Would you please upload a small repro project(zipped) to us for repro,
then I can perform some research on it directly...
(Please remove the "online" of my email address alias)


Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Please read my previous posting.

This has nothing to do with debug, it has to do with compiling.

I have just created a brand new C++ project and I get the same error, so
this sugests to me that it is in fact using the VC 6 compiler.

I tried reinstalling VS2005 but this did not help.
 
Sorry Michael, I mistyped, I wanted to mean the compiler instead.
I have just created a brand new C++ project and I get the same error,
so this sugests to me that it is in fact using the VC 6 compile.
Click to expand...

Do you mean you even cannot complie a genuine VC2005 project in your VS2005
IDE, if you type the "cl" in your Visual Studio 2005 Command Prompt console
window, which version will you find, the VC8 compiler's version should be
14.00.50727.


Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Yes, that is correct I can not even compile a genuine new vc2005 project.

When I open up a VC 2005 command prompt I get the correct version of cl

This is my path which looks to be extream ...

PATH=C:\Program Files\Microsoft Visual Studio 8\Common7\IDE;C:\Program
Files\Mic
rosoft Visual Studio 8\VC\BIN;C:\Program Files\Microsoft Visual Studio
8\Common7
\Tools;C:\Program Files\Microsoft Visual Studio
8\Common7\Tools\bin;C:\Program F
iles\Microsoft Visual Studio 8\VC\PlatformSDK\bin;C:\Program Files\Microsoft
Vis
ual Studio
8\SDK\v2.0\bin;C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727;C:\Progr
am Files\Microsoft Visual Studio
8\VC\VCPackages;C:\WINDOWS\system32;C:\WINDOWS;
C:\WINDOWS\System32\Wbem;C:\Program Files\QuickTime\QTSystem\;C:\Program
Files\M
icrosoft SQL Server\80\Tools\BINN;C:\Program Files\Common
Files\Adobe\AGL;C:\Pro
gram Files\Microsoft SQL Server\80\Tools\Binn\;C:\Program Files\Microsoft
SQL Se
rver\90\DTS\Binn\;C:\Program Files\Microsoft SQL
Server\90\Tools\binn\;C:\Progra
m Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\;C:\Program
Files
\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\;C:\Program
Files\Micro
soft Visual Studio\Common\Tools\WinNT;C:\Program Files\Microsoft Visual
Studio\C
ommon\MSDev98\Bin;C:\Program Files\Microsoft Visual
Studio\Common\Tools;C:\Progr
am Files\Microsoft Visual Studio\VC98\bin;

--
Michael Tissington
http://www.oaklodge.com
http://www.tabtag.com


"Gary Chang[MSFT]" said:
Sorry Michael, I mistyped, I wanted to mean the compiler instead.
I have just created a brand new C++ project and I get the same error,
so this sugests to me that it is in fact using the VC 6 compile.
Click to expand...

Do you mean you even cannot complie a genuine VC2005 project in your
VS2005
IDE, if you type the "cl" in your Visual Studio 2005 Command Prompt
console
window, which version will you find, the VC8 compiler's version should be
14.00.50727.


Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no
rights.
Click to expand...
 
Hi Michael,
Yes, that is correct I can not even compile a genuine new vc2005 project.
Click to expand...

If so, what's error message while you build a genuine VC2005 project?

Your PATH environment variable seems OK, and your VS2005 IDE will use the
path setting in the %VS8InstallDir%\Common7\Tools\vsvars32.bat first, I
don't think your VS2005 will use the VC6 compiler, I don't find any similar
case in our database.

By the way, is it possible to send us a simple repro sample project(zipped)
for test, currently we are unable to repro this problem in our side...


Thanks!

Best regards,

Gary Chang
Microsoft Community Support
--------------------
Get Secure! ¡§C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.asp
&SD=msdn

This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top