From owner-freebsd-current@FreeBSD.ORG Sat Mar 24 16:01:51 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E974106566B for ; Sat, 24 Mar 2012 16:01:51 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4F0428FC0C for ; Sat, 24 Mar 2012 16:01:51 +0000 (UTC) Received: by iahk25 with SMTP id k25so8043877iah.13 for ; Sat, 24 Mar 2012 09:01:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding; bh=gMvM2C7GJw53Kt5U5PVLiqAjxKxkRcvlh222qUMsD+A=; b=BL8yQFMZ/64v/rZOLr4QiDco7Ibs2c3GJMlVCp8vLPXzewJoutQgbgyxjp4ikxQENP 341tYE1F8l2hWBbCsT9wtcy8B7gq5DjCkTiXjPakHyu5uk1Fxvih3dxW5IKbzvyUuiOX KywYoD8sD1qK3YdmNS75EeIUPAsD4+n0PvOkaUWsW/sCxbXcY6bN5d4nWcuqQY1W3BLI 6u0rdBJ//39ioTNF8URAKrBJoZPiHK2ncIq5ANvnFKs3HZtFtVmYptSgGULkp9RdZ37+ KbbW4ACVS8Ioni76C+KLYMkiMQK0mMh0cAidzYVR6MZvzQh2GYf5bTZ0qseD2aMTKn5f eS7w== Received: by 10.42.131.7 with SMTP id x7mr10930458ics.40.1332604905506; Sat, 24 Mar 2012 09:01:45 -0700 (PDT) Received: from narn.knownspace (216-15-41-8.c3-0.gth-ubr1.lnh-gth.md.cable.rcn.com. [216.15.41.8]) by mx.google.com with ESMTPS id vr4sm13926576igb.1.2012.03.24.09.01.44 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 24 Mar 2012 09:01:45 -0700 (PDT) Date: Sat, 24 Mar 2012 12:01:40 -0400 From: Justin Hibbits To: Super Bisquit Message-ID: <20120324120140.504751b6@narn.knownspace> In-Reply-To: References: X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; powerpc-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current Subject: Re: general clang error: cause for worry? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2012 16:01:51 -0000 On Sat, 24 Mar 2012 11:58:04 -0400 Super Bisquit wrote: > ---------- Forwarded message ---------- > From: Super Bisquit > Date: Fri, Mar 16, 2012 at 11:17 PM > Subject: general clang error: cause for worry? > To: brooks@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