libLTO warning

Hi all,

I just svn-updated the 2.5 branch on my machine and I noticed this warning during the build.

*** Warning: Linking the shared library /home/maurice/installation/llvm/Debug/lib/libLTO.la against the non-libtool
*** objects /home/maurice/installation/llvm/Debug/lib/LLVMCppBackend.o /home/maurice/installation/llvm/Debug/lib/LLVMMSIL.o /home/maurice/installation/llvm/Debug/lib/LLVMCBackend.o /home/maurice/installation/llvm/Debug/lib/LLVMXCore.o /home/maurice/installation/llvm/Debug/lib/LLVMPIC16.o /home/maurice/installation/llvm/Debug/lib/LLVMCellSPUCodeGen.o /home/maurice/installation/llvm/Debug/lib/LLVMCellSPUAsmPrinter.o /home/maurice/installation/llvm/Debug/lib/LLVMMips.o /home/maurice/installation/llvm/Debug/lib/LLVMARMAsmPrinter.o /home/maurice/installation/llvm/Debug/lib/LLVMARMCodeGen.o /home/maurice/installation/llvm/Debug/lib/LLVMIA64.o /home/maurice/installation/llvm/Debug/lib/LLVMAlphaCodeGen.o /home/maurice/installation/llvm/Debug/lib/LLVMAlphaAsmPrinter.o /home/maurice/installation/llvm/Debug/lib/LLVMPowerPCAsmPrinter.o /home/maurice/installation/llvm/Debug/lib/LLVMPowerPCCodeGen.o /home/maurice/installation/llvm/Debug/lib/LLVMSparcCodeGen.o /home/maurice/installation/llvm/Debug/lib/LLVMSparcAsmPrinter.o /home/maurice/installation/llvm/Debug/lib/LLVMX86AsmPrinter.o /home/maurice/installation/llvm/Debug/lib/LLVMX86CodeGen.o is not portable!

I haven’t noticed any ill-effects. Is this a harmless warning or does it need to be fixed?

I’m on Linux/Fedora 9, x86-64.

Kind regards,
Maurice

Maurice Gittens wrote:

Hi all,

I just svn-updated the 2.5 branch on my machine and I noticed this warning during the build.

*** Warning: Linking the shared library /home/maurice/installation/llvm/Debug/lib/libLTO.la against the non-libtool
*** objects /home/maurice/installation/llvm/Debug/lib/LLVMCppBackend.o /home/maurice/installation/llvm/Debug/lib/LLVMMSIL.o /home/maurice/installation/llvm/Debug/lib/LLVMCBackend.o /home/maurice/installation/llvm/Debug/lib/LLVMXCore.o /home/maurice/installation/llvm/Debug/lib/LLVMPIC16.o /home/maurice/installation/llvm/Debug/lib/LLVMCellSPUCodeGen.o /home/maurice/installation/llvm/Debug/lib/LLVMCellSPUAsmPrinter.o /home/maurice/installation/llvm/Debug/lib/LLVMMips.o /home/maurice/installation/llvm/Debug/lib/LLVMARMAsmPrinter.o /home/maurice/installation/llvm/Debug/lib/LLVMARMCodeGen.o /home/maurice/installation/llvm/Debug/lib/LLVMIA64.o /home/maurice/installation/llvm/Debug/lib/LLVMAlphaCodeGen.o /home/maurice/installation/llvm/Debug/lib/LLVMAlphaAsmPrinter.o /home/maurice/installation/llvm/Debug/lib/LLVMPowerPCAsmPrinter.o /home/maurice/installation/llvm/Debug/lib/LLVMPowerPCCodeGen.o /home/maurice/installation/llvm/Debug/lib/LLVMSparcCodeGen.o /home/maurice/installation/llvm/Debug/lib/LLVMSparcAsmPrinter.o /home/maurice/installation/llvm/Debug/lib/LLVMX86AsmPrinter.o /home/maurice/installation/llvm/Debug/lib/LLVMX86CodeGen.o is not portable!

I haven't noticed any ill-effects. Is this a harmless warning or does it need to be fixed?

I'm on Linux/Fedora 9, x86-64.

The warnings are harmless, but regardless libLTO shouldn't be trying to build on any platform except Darwin.

It looks like the 2.5 rebranching took place at just the wrong time and picked up a change when I tried to have libLTO build on Linux as well. That change should never have made it into the 2.5 branch.

Tanya, could you please revert 62987 from the 2.5 branch? It's this patch:
http://llvm.org/viewvc/llvm-project/llvm/branches/release_25/tools/Makefile?r1=62895&r2=62987

fortunately just a one-liner. I'm really sorry for the trouble...

Nick

Nick Lewycky wrote:

Maurice Gittens wrote:

Hi all,

I just svn-updated the 2.5 branch on my machine and I noticed this warning during the build.

*** Warning: Linking the shared library /home/maurice/installation/llvm/Debug/lib/libLTO.la against the non-libtool
*** objects /home/maurice/installation/llvm/Debug/lib/LLVMCppBackend.o /home/maurice/installation/llvm/Debug/lib/LLVMMSIL.o /home/maurice/installation/llvm/Debug/lib/LLVMCBackend.o /home/maurice/installation/llvm/Debug/lib/LLVMXCore.o /home/maurice/installation/llvm/Debug/lib/LLVMPIC16.o /home/maurice/installation/llvm/Debug/lib/LLVMCellSPUCodeGen.o /home/maurice/installation/llvm/Debug/lib/LLVMCellSPUAsmPrinter.o /home/maurice/installation/llvm/Debug/lib/LLVMMips.o /home/maurice/installation/llvm/Debug/lib/LLVMARMAsmPrinter.o /home/maurice/installation/llvm/Debug/lib/LLVMARMCodeGen.o /home/maurice/installation/llvm/Debug/lib/LLVMIA64.o /home/maurice/installation/llvm/Debug/lib/LLVMAlphaCodeGen.o /home/maurice/installation/llvm/Debug/lib/LLVMAlphaAsmPrinter.o /home/maurice/installation/llvm/Debug/lib/LLVMPowerPCAsmPrinter.o /home/maurice/installation/llvm/Debug/lib/LLVMPowerPCCodeGen.o /home/maurice/installation/llvm/Debug/lib/LLVMSparcCodeGen.o /home/maurice/installation/llvm/Debug/lib/LLVMSparcAsmPrinter.o /home/maurice/installation/llvm/Debug/lib/LLVMX86AsmPrinter.o /home/maurice/installation/llvm/Debug/lib/LLVMX86CodeGen.o is not portable!

I haven't noticed any ill-effects. Is this a harmless warning or does it need to be fixed?

I'm on Linux/Fedora 9, x86-64.

The warnings are harmless, but regardless libLTO shouldn't be trying to build on any platform except Darwin.

It looks like the 2.5 rebranching took place at just the wrong time and picked up a change when I tried to have libLTO build on Linux as well. That change should never have made it into the 2.5 branch.

Tanya, could you please revert 62987 from the 2.5 branch? It's this patch:
http://llvm.org/viewvc/llvm-project/llvm/branches/release_25/tools/Makefile?r1=62895&r2=62987

fortunately just a one-liner. I'm really sorry for the trouble...

BTW, this has already been reverted on trunk. Here's the revert:
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20090209/073590.html