can't build with just the CppBackend

[llvmbot]

Bugzilla Link	3368
Version	2.4
OS	Windows XP
Attachments	suggested fix for linker errors
Reporter	LLVM Bugzilla Contributor
CC	@isanbard,@jayfoad

Extended Description

On Linux/x86 I did:

$ ../llvm-2.4/configure --enable-targets=cbe ; make

It fails with:

llvm[2]: Linking Release executable llc (without symbols)
/home/foad/llvm/objdir-poo/tools/llc/Release/llc.o: In function global constructors keyed to FileType': llc.cpp:(.text+0x93d): undefined reference to llvm::createBURRListDAGScheduler(llvm::SelectionDAGISel*, llvm::SelectionDAG*, llvm::MachineBasicBlock*, bool)'
llc.cpp:(.text+0x961): undefined reference to llvm::createTDRRListDAGScheduler(llvm::SelectionDAGISel*, llvm::SelectionDAG*, llvm::MachineBasicBlock*, bool)' llc.cpp:(.text+0x985): undefined reference to llvm::createTDListDAGScheduler(llvm::SelectionDAGISel*, llvm::SelectionDAG*, llvm::MachineBasicBlock*, bool)'
llc.cpp:(.text+0x9a9): undefined reference to llvm::createFastDAGScheduler(llvm::SelectionDAGISel*, llvm::SelectionDAG*, llvm::MachineBasicBlock*, bool)' llc.cpp:(.text+0x9cd): undefined reference to llvm::createDefaultScheduler(llvm::SelectionDAGISel*, llvm::SelectionDAG*, llvm::MachineBasicBlock*, bool)'
llc.cpp:(.text+0x9d7): undefined reference to `llvm::linkOcamlGCPrinter()'
collect2: ld returned 1 exit status
make[2]: *** [/home/foad/llvm/objdir-poo/Release//bin/llc] Error 1

I would find it useful to be able to build llc without any of the native codegen backends.

[lattner]

Hi Jay, does this patch still work? Is this still a problem?

[llvmbot]

suggested fix for llvm-gcc linker errors

does this patch still work? Is this still a problem?

Yes and yes! Can I apply it?

I'm also attaching a patch for a similar problem in llvm-gcc. llvm_initialize_backend() in llvm-backend.cpp calls createDefaultScheduler, which is defined in SelectionDAGISel.cpp, so cc1(plus) needs to be linked with libLLVMSelectionDAG.a. Normally this problem is masked because cc1(plus) is linked with a real target back end, which includes the SelectionDAG stuff, but when we configure llvm-gcc for a proprietary standalone backend we get more linker errors. Is this patch OK to apply?

[llvmbot]

suggested fix for llvm-gcc linker errors

does this patch still work? Is this still a problem?

Yes and yes! Can I apply it?

I'm also attaching a patch for a similar problem in llvm-gcc. llvm_initialize_backend() in llvm-backend.cpp calls createDefaultScheduler, which is defined in SelectionDAGISel.cpp, so cc1(plus) needs to be linked with libLLVMSelectionDAG.a. Normally this problem is masked because cc1(plus) is linked with a real target back end, which includes the SelectionDAG stuff, but when we configure llvm-gcc for a proprietary standalone backend we get more linker errors. Is this patch OK to apply?

[llvmbot]

suggested fix for llvm-gcc linker errors
I accidentally attached the llvm-gcc patch twice, so I'm marking one of them as obsolete.

[llvmbot]

suggested fix for linker errors
Patch updated to apply to svn trunk rev 93423.

[jayfoad]

I still get this problem if I configure with --enable-targets=cpp (instead of =cbe).

[isanbard]

The C backend doesn't exist anymore.

[jayfoad]

The C backend doesn't exist anymore.

True, but this bug is now about CppBackend, which does exist. See the summary and comment 7.

[asl]

cppbackend does not exist either