From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GupQK-0006rq-Dm for qemu-devel@nongnu.org; Thu, 14 Dec 2006 07:10:52 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GupQI-0006qz-Mr for qemu-devel@nongnu.org; Thu, 14 Dec 2006 07:10:51 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GupQI-0006qt-HY for qemu-devel@nongnu.org; Thu, 14 Dec 2006 07:10:50 -0500 Received: from [64.233.182.184] (helo=nf-out-0910.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GupQI-00044d-5D for qemu-devel@nongnu.org; Thu, 14 Dec 2006 07:10:50 -0500 Received: by nf-out-0910.google.com with SMTP id c31so1093416nfb for ; Thu, 14 Dec 2006 04:10:49 -0800 (PST) Message-ID: Date: Thu, 14 Dec 2006 13:10:48 +0100 From: "G Portokalidis" Subject: Re: [Qemu-devel] Compiling qemu as position-independent code on an x86_64 linux host In-Reply-To: <61EB814CF63D9642BA6DD5B76DB0894306DA81@mx-met-exch0.scisys.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <61EB814CF63D9642BA6DD5B76DB0894306DA81@mx-met-exch0.scisys.co.uk> 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 Cc: Paul.Robinson@scisys.co.uk Hello Paul, I also need to use qemu as a shared library, so i was wandering whether you had any luck with this? On 03/11/06, Paul Robinson wrote: > > > > Hi guys, > > I'm trying to use parts of qemu in an application that must be compiled as a > shared library (i.e. a .so file). > The code must be compiled with the -fPIC option otherwise the linker refuses > to create a .so file > but doing this causes dyngen to stop with the error: > ../dyngen -o op.h op.o > dyngen: unsupported X86_64 relocation (9) > > In dyngen-exec.h, if I change > extern int __op_param1, __op_param2, __op_param3; > to > static int __op_param1, __op_param2, __op_param3; > then dyngen stops with > dyngen: unsupported X86_64 relocation (4) > > I suspect that I need to resort to assembly language (as has been done for > alpha hosts). > > My question is: > Has anyone already done this ? (so I don't have to re-invent the wheel). > > The nearest I've found so far is Johannes Schindelin's "Porting QEMU to [a] > new CPU" guide. > > Regards, > Paul R. > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel > > >