llvm dev - May 2010 - [LLVMdev] Linking problems with llvm-2.7, release 64b build with vs2010

Hello,

Following some recent messages about building with Visual Studio 2010,
I have gotten most things to compile in release mode on 64b windows 7.
(Mainly the few errors with 0 -> nullptr in the second argument of the
pair constructor, and making an ECValue constructor public).

I'm falling at the last hurdle though when it comes to the final link:

1>------ Build started: Project: Fibonacci, Configuration: Release x64 ------
1>     Creating library
C:/llvm-2.7-src/build/lib/Release/Fibonacci.lib and object
C:/llvm-2.7-src/build/lib/Release/Fibonacci.exp
1>LLVMX86CodeGen.lib(X86JITInfo.obj) : error LNK2019: unresolved
external symbol X86CompilationCallback referenced in function "public:
virtual void (__cdecl*__cdecl
llvm::X86JITInfo::getLazyResolverFunction(void * (__cdecl*)(void
*)))(void)" (?getLazyResolverFunction at
X86JITInfo@llvm@@UEAAP6AXXZP6APEAXPEAX at Z@Z)
1>C:\llvm-2.7-src\build\bin\Release\Fibonacci.exe : fatal error
LNK1120: 1 unresolved externals
========== Build: 0 succeeded, 1 failed, 22 up-to-date, 0 skipped =========
I'm not entirely convinced that
lib/Target/X86/X86CompilationCallback_Win64.asm is being assembled and
linked into that library - has anyone gotten this to link properly?

thanks
b

"Bill O'Hara" <billtohara at gmail.com> writes:
> 1>LLVMX86CodeGen.lib(X86JITInfo.obj) : error LNK2019: unresolved
> external symbol X86CompilationCallback referenced in function "public:
> virtual void (__cdecl*__cdecl
> llvm::X86JITInfo::getLazyResolverFunction(void * (__cdecl*)(void
> *)))(void)" (?getLazyResolverFunction at
X86JITInfo@llvm@@UEAAP6AXXZP6APEAXPEAX at Z@Z)
> 1>C:\llvm-2.7-src\build\bin\Release\Fibonacci.exe : fatal error
> LNK1120: 1 unresolved externals
> ========== Build: 0 succeeded, 1 failed, 22 up-to-date, 0 skipped
=========>
> I'm not entirely convinced that
> lib/Target/X86/X86CompilationCallback_Win64.asm is being assembled and
> linked into that library - has anyone gotten this to link properly?
See if this bug report helps you to work around the problem:

http://www.llvm.org/bugs/show_bug.cgi?id=4936

Please report your results.

On 2010-05-13 01:37, Óscar Fuentes wrote:
>> lib/Target/X86/X86CompilationCallback_Win64.asm is being assembled and
>> linked into that library - has anyone gotten this to link properly?
> 
> See if this bug report helps you to work around the problem:
> 
> http://www.llvm.org/bugs/show_bug.cgi?id=4936
It indeed looks like a CMake issue; see this report:

http://public.kitware.com/Bug/view.php?id=8170

As far as I can see, none of the code posted in that report has yet made
it to the CMake git repository, though.