Re: general clang error: cause for worry?

On Sat, 24 Mar 2012 11:58:04 -0400
Super Bisquit <superbisquit_at_gmail.com> wrote:

> ---------- Forwarded message ----------
> From: Super Bisquit <superbisquit_at_gmail.com>
> Date: Fri, Mar 16, 2012 at 11:17 PM
> Subject: general clang error: cause for worry?
> To: brooks_at_freebsd.org
> 
> 
> chipchop# pkg_info|grep clang
> clang-3.0           C, Objective-C, and (alpha-quality) C++ compiler
> chipchop# pkg_info | grep llvm
> llvm-3.0            Low Level Virtual Machine
> chipchop# ls /usr/bin/cl*
> /usr/bin/clang        /usr/bin/clang++    /usr/bin/clear
> chipchop# /usr/bin/clang --version
> FreeBSD clang version 2.8 (tags/RELEASE_28 115870) 20101007
> Target: powerpc-undermydesk-freebsd9.0
> Thread model: posix
> chipchop# ls /usr/local/bin/cl*
> /usr/local/bin/clang        /usr/local/bin/clang-tblgen
> /usr/local/bin/clearspd
> /usr/local/bin/clang++        /usr/local/bin/cleanlinks
> chipchop# ls /usr/local/bin/clang --version
> ls: --version: No such file or directory
> /usr/local/bin/clang
> chipchop#  /usr/local/bin/clang --version
> /libexec/ld-elf.so.1: /usr/local/lib/libLLVM-3.0.so: Unsupported
> relocation type 10 in non-PLT relocations
> 
> chipchop#
> 
> As in my response to Dimitri, this is the error.
> If this error occurs on the real machine, it will occur on Tinderbox.

Yes, the ports clang does have a problem, because it's built with
shared libraries.  I've reported it (tacked onto an existing report) to
llvm.  The cause is that there is a symbol in the PowerPC JIT code
that's naked (no PIC annotations), so the shared library fails to load
at runtime. I will submit a separate bug report to llvm in the near
future, just so it doesn't get lost.

- Justin