From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HhxJb-00055U-Uz for qemu-devel@nongnu.org; Sat, 28 Apr 2007 20:30:59 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HhxJa-00052n-Oh for qemu-devel@nongnu.org; Sat, 28 Apr 2007 20:30:59 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HhxJa-00052X-IT for qemu-devel@nongnu.org; Sat, 28 Apr 2007 20:30:58 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1HhxDZ-00070J-2X for qemu-devel@nongnu.org; Sat, 28 Apr 2007 20:24:45 -0400 From: Paul Brook Subject: Re: [Qemu-devel] Sparc-linux-user problem Date: Sun, 29 Apr 2007 01:24:40 +0100 References: <200704281820.57259.paul@codesourcery.com> <20070428213912.3bc3ce6b@c1358217.kevquinn.com> In-Reply-To: <20070428213912.3bc3ce6b@c1358217.kevquinn.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200704290124.40951.paul@codesourcery.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Saturday 28 April 2007, Kevin F. Quinn wrote: > On Sat, 28 Apr 2007 18:20:55 +0100 > > Paul Brook wrote: > > On Saturday 28 April 2007, Blue Swirl wrote: > > > Hi, > > > > > > I'm investigating why Sparc32 user emulator breaks when linked with > > > -lrt. It seems that other libraries also cause the problem, for > > > example -lm -ldl -lX11 -lbfd -lslang is okay, but -lm -ldl -lX11 > > > -lbfd -lslang -lglib-2.0 segfaults just like -lm -lrt. If just > > > address space conflict was the issue, I'd think 12 megs libbfd > > > would trigger the problem instead of 64k librt. > > > > > > Any ideas? > > > > I've never got this to work reliably on either x86 or amd64 hosts. I > > get mysterious segfaults in the depths of libc. My guess is that the > > tricks qemu uses to link itself as a shared library are confusing > > things (possibly the TLS initialisation). > > I don't suppose using gcc/binutils -fPIE/-pie would achieve qemu's > goals, thus avoiding the need to specify bespoke ld scripts? Sort-of, maybe. Paul