Svadev mailing list

[John Criswell <criswell AT illinois.edu>]

On 12/4/12 11:45 AM, Tom Roeder wrote:

Hi, 

I just grabbed the latest SAFECode release (following the instructions at http://safecode.cs.illinois.edu/downloads.html for LLVM 3.2); the SAFECode branch that I have is currently at rev 169035.

But when I try to build, I get linking errors about "anonymous version tag cannot be combined with other version tags".  The tail of the build is as follows:

llvm[4]: Compiling CXType.cpp for Release build (PIC)

llvm[4]: Compiling IndexBody.cpp for Release build (PIC)

llvm[4]: Compiling IndexDecl.cpp for Release build (PIC)

llvm[4]: Compiling IndexTypeSourceInfo.cpp for Release build (PIC)

llvm[4]: Compiling Indexing.cpp for Release build (PIC)

llvm[4]: Compiling IndexingContext.cpp for Release build (PIC)

llvm[4]: Linking Release Shared Library libclang.so

llvm[4]: Building Release Archive Library libclang.a

/usr/bin/ld: anonymous version tag cannot be combined with other version tags

collect2: ld returned 1 exit status

make[4]: *** [/home/tmroeder/src/llvm/projects/safecode/Release/lib/libclang.so] Error 1

make[4]: Leaving directory `/home/tmroeder/src/llvm/projects/safecode/tools/clang/tools/libclang'

make[3]: *** [all] Error 1

make[3]: Leaving directory `/home/tmroeder/src/llvm/projects/safecode/tools/clang/tools'

make[2]: *** [all] Error 1

make[2]: Leaving directory `/home/tmroeder/src/llvm/projects/safecode/tools/clang'

make[1]: *** [clang/.makeall] Error 2

make[1]: Leaving directory `/home/tmroeder/src/llvm/projects/safecode/tools'

make: *** [all] Error 1

I don't believe anyone has found a solution to this problem (other than hacking the Makefiles to build only the compiler front-end which, for SAFECode, is the only component that is really needed).  Part of the reason why I haven't looked closer into it is that the problem doesn't occur on any of our Linux machines and, until now, I didn't think it affected that many people.

I don't suppose you've tested on Scientific Linux 6?  If not, I think the only way I can fix the problem is to create a VMWare virtual machine image with Ubuntu.  I can try to take a look at it either later this week or early next week.

Can you file a bug report with these details?

-- John T.

I configured and ran the build from the top-level llvm directory as follows:

./configure --enable-optimized --disable-assertions && make -j4 tools-only && cd projects/poolalloc && make -j4 && cd ../safecode && make -j4

And my ld and gcc report the following versions

GNU ld (GNU Binutils for Ubuntu) 2.22

gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3

I have reproduced this problem in multiple configurations and on multiple machines (including building this with clang instead of gcc).  Just to get an easily repro'd config, the previous results are from a stock virtual machine version of Ubuntu Precise:

Ubuntu 12.04.1 LTS (GNU/Linux 2.6.39-gcg-20121018 x86_64)

The only change I made to the installation was to apt-get install g++ and subversion.

I see that there was a similar thread on svadev in September about a similar problem, and I can confirm the comment (http://lists.cs.uiuc.edu/pipermail/svadev/2012-September/000388.html) from that thread that says removing everything but the driver target from tools/clang/tools/Makefile allows clang to build correctly. Adding back any of the other targets (libclang c-index-test arcmt-test c-arcmt-test diagtool clang-check) causes the same error from ld.

Has anyone found a solution to this problem?

Thanks,

Tom Roeder

_______________________________________________
svadev mailing list
svadev AT cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/svadev