[LLVMdev] llvm-mc build fails

[John Myers]

Hi Óscar,

Thanks for the explanation. I was able to use the automatic update method.
FYI, for some reason the first run build completed without failure.

--John

On Mon, Nov 2, 2009 at 2:28 AM, Óscar Fuentes <ofv at wanadoo.es> wrote:

> The following message is a courtesy copy of an article
> that has been posted to gmane.comp.compilers.llvm.devel as well.
>
> John Myers <atomicdog.jwm at gmail.com> writes:
>
> > I'm looking for some pointers on how to troubleshoot this problem. I'm
> > trying to write a backend for the AVR.
> > There is an undefined reference at line 48 which is the line FrameInfo()
> is
> > on. I've tried to use the MSP430 and other targets as references so I'm
> not
> > sure
> > what changes I did would cause a problem on this line?
>
> cmake tracks library dependencies on
> $LLVM_ROOT/cmake/modules/LLVMLibDeps.txt
>
> That file is automatically updated on Unix and Unix-like platforms when
> all LLVM targets are included on the build. This means that either you
> update the file manually or run the build with MSYS passing
> -DLLVM_TARGETS_TO_BUILD=all on the cmake command line.
>
> The manual update would consist on adding this lines to the above
> mentioned file:
>
> set(MSVC_LIB_DEPS_LLVMAVRAsmPrinter LLVMAsmPrinter LLVMCodeGen LLVMCore
> LLVMMC LLVMAVRInfo LLVMSupport LLVMSystem LLVMTarget)
> set(MSVC_LIB_DEPS_LLVMAVRCodeGen LLVMCodeGen LLVMCore LLVMMC LLVMAVRInfo
> LLVMSelectionDAG LLVMSupport LLVMSystem LLVMTarget)
> set(MSVC_LIB_DEPS_LLVMAVRInfo LLVMSupport)
>
> which uses MSP430 as a template and supposses that your target is named
> `AVR' (case sensitive).
>
> In case you use the automatic update, the first run of the build will
> fail because the new dependencies are still not effective. Re-execute
> the build and it should work.
>
> --
> Óscar
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20091102/a3e8201f/attachment.html>