From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1Bk8U5-0005Yh-3c for qemu-devel@nongnu.org; Mon, 12 Jul 2004 17:37:13 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1Bk8U2-0005Y2-ST for qemu-devel@nongnu.org; Mon, 12 Jul 2004 17:37:12 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1Bk8U2-0005Xl-NP for qemu-devel@nongnu.org; Mon, 12 Jul 2004 17:37:10 -0400 Received: from [194.90.9.29] (helo=mxout5.netvision.net.il) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Bk8R8-0004A3-L5 for qemu-devel@nongnu.org; Mon, 12 Jul 2004 17:34:10 -0400 Received: from [10.0.0.150] ([212.235.101.134]) by mxout5.netvision.net.il (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTPA id <0I0R00KEBD8WDP@mxout5.netvision.net.il> for qemu-devel@nongnu.org; Tue, 13 Jul 2004 00:34:08 +0300 (IDT) Date: Wed, 14 Jul 2004 00:34:17 +0300 From: Hetz Ben Hamo Subject: Re: [Qemu-devel] SDL, GLIBC_PRIVATE error for __libc_sigaction In-reply-to: Message-id: <40F45559.2080909@witch.dyndns.org> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT References: 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, paul@clubi.ie Do: LD_ASSUME_KERNEL=2.2.5 qemu Thanks, Hetz Paul Jakma wrote: > Hi, > > I get the following error trying to run qemu compiled with SDL support: > > ./i386-softmmu/qemu: relocation error: ./i386-softmmu/qemu: symbol > __libc_sigaction, version GLIBC_PRIVATE not defined in file libc.so.6 > with link time reference > > This is on FC2 x86_64. AFAICT. Judging by posts like: > > http://sources.redhat.com/ml/libc-hacker/2004-05/msg00001.html > > The glibc folks are rather keen to not have GLIBC_PRIVATE symbols be > used outside of libc ;) (that patch doesnt remove __libc_sigaction > AFAICT, but I guess it's been removed since then. > > Is there any workaround for this? (other than not using SDL support). > > regards,