From owner-freebsd-arm@FreeBSD.ORG Sat Jun 9 18:12:39 2012 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1D33106566B; Sat, 9 Jun 2012 18:12:39 +0000 (UTC) (envelope-from gonzo@hq.bluezbox.com) Received: from hq.bluezbox.com (hq.bluezbox.com [70.38.37.145]) by mx1.freebsd.org (Postfix) with ESMTP id 7A88F8FC08; Sat, 9 Jun 2012 18:12:39 +0000 (UTC) Received: from [207.6.240.242] (helo=[192.168.1.64]) by hq.bluezbox.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.73 (FreeBSD)) (envelope-from ) id 1SdQ90-0002nI-Ke; Sat, 09 Jun 2012 11:12:17 -0700 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1463\)) From: Oleksandr Tymoshenko In-Reply-To: <2EB675BD-4275-4E05-B551-CAF92584E9BC@freebsd.org> Date: Sat, 9 Jun 2012 11:12:03 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <1199EB69-28A3-4F5F-AAAD-FA6A52063F4B@bluezbox.com> References: <2EB675BD-4275-4E05-B551-CAF92584E9BC@freebsd.org> To: Tim Kientzle X-Mailer: Apple Mail (2.1463) Sender: gonzo@hq.bluezbox.com X-Spam-Level: ---- X-Spam-Report: Spam detection software, running on the system "hq.bluezbox.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: On 2012-06-09, at 9:20 AM, Tim Kientzle wrote: > In the armv6 tree, libc.so fails to link with an error because DT_TEXTREL is being generated. But I can't figure out why this is happening: > > * A regular arm.arm libc.so built on -CURRENT does not have a TEXTREL section. > > * This first appeared in gonzo's "Huge merge from HEAD" at commit 234858. An armv6 world from r234857 doesn't have a TEXTREL in libc.so. > > * I cannot find any interesting differences in the Makefiles under libc that might explain this. That commit did not merge any interesting changes to binutils, either. > > * If I make the --warn-shared-textrel non-fatal, then libc.so can build successfully. > = It does indeed have a TEXTREL section, BUT > = that section is zero bytes long (if I'm reading objdump output correctly) > (So I understand neither why it's there nor why it's presence would be a problem.) > > Any ideas for what I should check next? [...] Content analysis details: (-4.4 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Cc: arm@freebsd.org Subject: Re: armv6 tree broken with DT_TEXTREL error in libc.so X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jun 2012 18:12:39 -0000 On 2012-06-09, at 9:20 AM, Tim Kientzle wrote: > In the armv6 tree, libc.so fails to link with an error because = DT_TEXTREL is being generated. But I can't figure out why this is = happening: >=20 > * A regular arm.arm libc.so built on -CURRENT does not have a TEXTREL = section. >=20 > * This first appeared in gonzo's "Huge merge from HEAD" at commit = 234858. An armv6 world from r234857 doesn't have a TEXTREL in libc.so. >=20 > * I cannot find any interesting differences in the Makefiles under = libc that might explain this. That commit did not merge any interesting = changes to binutils, either. >=20 > * If I make the --warn-shared-textrel non-fatal, then libc.so can = build successfully. > =3D It does indeed have a TEXTREL section, BUT > =3D that section is zero bytes long (if I'm reading objdump = output correctly) > (So I understand neither why it's there nor why it's presence = would be a problem.) >=20 > Any ideas for what I should check next? Hmm, I thought I fixed it with r236527. Do you have this change in your = tree?