From owner-freebsd-current@FreeBSD.ORG Mon May 27 20:08:44 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5ABE1FF8 for ; Mon, 27 May 2013 20:08:44 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) by mx1.freebsd.org (Postfix) with ESMTP id 2091B9A0 for ; Mon, 27 May 2013 20:08:43 +0000 (UTC) Received: from coleburn.home.andric.com (coleburn.home.andric.com [192.168.0.15]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 3E62A5C44; Mon, 27 May 2013 22:08:40 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: Building of libc in /usr/src/lib/libc results in error From: Dimitry Andric In-Reply-To: <51A39602.7010604@gmx.com> Date: Mon, 27 May 2013 22:08:39 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <51A39602.7010604@gmx.com> To: dt71@gmx.com X-Mailer: Apple Mail (2.1503) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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: Mon, 27 May 2013 20:08:44 -0000 On May 27, 2013, at 19:21, dt71@gmx.com wrote: > On 05/27/2013 02:28, Super Bisquit wrote: >> building shared library libc.so.7 >> /usr/bin/ld: warning: creating a DT_TEXTREL in a shared object. >=20 > I have run into this issue multiple times in the past -- its = occurrence seems to be correlated with header updates. As an instant = workaround, you can add ALLOW_SHARED_TEXTREL=3D1 to /etc/make.conf for = one buildworld&installworld run, and then do another run, for which = ALLOW_SHARED_TEXTREL=3D1 will empirically not be required. This may work around the issue, but it will not solve the root cause. Normally, you should never get these warnings, so there must be something special about your environment. Can you post your make.conf, src.conf and any other relevant settings? -Dimitry