LNK1254, LNK1284, and LNK1235 linker errors may occur while compiling a C source file with the /clr compiler option (822329)

SYMPTOMS

When you compile a C source file (unmanaged source) with other managed source files that refer to symbols that are defined in the unmanaged source, and you specify the /clr compiler switch, you receive the following linker error message in Visual C++ .NET 2002:

LINK : fatal error LINK1254: metadata for symbol symbol name inconsistent with COFF symbol table

You receive the following linker errors in Visual C++ .NET 2003:

<managed object file>: fatal error LNK1284: metadata inconsistent with COFF symbol table: symbol '<symbol-name>' (0A000008) mapped to '<symbol-name>' (06000001) in <unmanaged object file>

<unmanaged object file>: fatal error LNK1235: corrupt or invalid COFF symbol table

RESOLUTION

Compile the unmanaged source (including the C source files) into an object file. Similarly, compile files that constitute the managed files of the project into another object file. Link the object files that are generated from the managed and unmanaged source files into a single executable by using the linker. The following steps assume that you have unmanaged source in UnManaged.c and that you have managed source in Managed.cpp. To build your project, follow these steps:

Compile UnManaged.c with the following command:
```
cl /c UnManaged.c
```
Compile Managed.cpp with the following command:
```
cl /clr /c Managed.cpp
```
Link the object files that are generated in steps 1 and 2 with the following command:
```
link /NODEFAULTLIB:LIBC Managed.obj UnManaged.obj
```

MORE INFORMATION

Steps to Reproduce the Behavior

Paste the following code in Notepad, and then save the file as UnManaged.h:

#include <stdio.h>

// Both of these generate LNK1254 in 2002

//Generates LNK1235 - In 2003
//int willNotLink(unsigned char data[20]);
//int willLink(unsigned char *data);

//Generates LNK1284 - In 2003
int willLink(unsigned char data[20]);
int willNotLink(unsigned char *data);

Paste the following code in Notepad, and then save the file as UnManaged.c:

//defines two functions to be referred in a C++ file.
#include "UnManaged.h"

int willLink(unsigned char *data)
{
	printf("This is the function named willLink\n");
	return 0;
}

int willNotLink(unsigned char data[20])
{
	printf("This is the function named willNotLink\n");
	return 0;
}

Paste the following code in Notepad, and then save the file as Managed.cpp:

// This is the main file.

#pragma once

extern "C"
{
#include "UnManaged.h"
}

#using <mscorlib.dll>

using namespace System;

namespace LinkerProblem
{
	public __gc class Class1
	{
	public:
		void test()
		{
			unsigned char data[20];
			
			willLink(data);

			willNotLink(data);
		}
	};
};

void main()
{
	LinkerProblem::Class1 *myClass = new LinkerProblem::Class1();
	myClass->test();
}

At the Visual C++ .NET command prompt, type the following command:
```
cl /clr Managed.cpp UnManaged.c
```
Notice that you receive the linker problem that is described in the "Symptoms" section. In Visual C++ .NET 2002, you receive the LNK1254 linker error, and in Visual C++ .NET 2003 you receive the LNK1284 linker error.
To see the LNK1235 linker error in Visual C++ .NET 2003, modify the contents of the UnManaged.h header file. To do this, uncomment the two declarations under the following comment:
```
//Generates LNK1235 - In 2003
```
and then comment the two declarations under the following comment:
```
//Generates LNK1284 - In 2003
```
Compile the code by running the command that is specified in step 4 at the Visual Studio .NET 2003 command prompt. You receive the LNK1235 linker error in Visual C++ .NET 2003.

LNK1254, LNK1284, and LNK1235 linker errors may occur while compiling a C source file with the /clr compiler option (822329)

SYMPTOMS

CAUSE

RESOLUTION

STATUS

MORE INFORMATION

Steps to Reproduce the Behavior