From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DNol8-000479-MC for qemu-devel@nongnu.org; Tue, 19 Apr 2005 05:11:06 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DNol6-00046R-3x for qemu-devel@nongnu.org; Tue, 19 Apr 2005 05:11:06 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DNol5-00042E-Tv for qemu-devel@nongnu.org; Tue, 19 Apr 2005 05:11:04 -0400 Received: from [212.202.201.52] (helo=nb.nb) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DNomC-0007xi-Uo for qemu-devel@nongnu.org; Tue, 19 Apr 2005 05:12:13 -0400 Received: from [192.168.145.2] (helo=navaho) by nb.nb with esmtp (Exim 3.36 #1 (Debian)) id 1DNoq0-0007uK-00 for ; Tue, 19 Apr 2005 11:16:09 +0200 Received: from navaho ([127.0.0.1]) by navaho with esmtp (Exim 3.36 #1 (Debian)) id 1DNokQ-0001i0-00 for ; Tue, 19 Apr 2005 17:10:22 +0800 Message-ID: <4264CAFD.9050008@gmail.com> Date: Tue, 19 Apr 2005 17:10:21 +0800 From: Sebastian Nowozin MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Possible?: statically converting i386 ELF object files to ARM ELF object files 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 Hello everybody, (please quote my email address on a reply to this email, I am not member of the list, thanks.) I have wondered wether the code conversion ability of qemu could be utilized to convert ELF .o object files compiled for i386 Linux by GCC to .o object files for ARM/Linux. Is this possible or has something been attempted in this direction? The need for such conversion occurs when porting the Java MIDP to ARM. Due to export restrictions, for some cryptography code in the MIDP, only linkable object files for i386 are available with the sources. (Half a dozen small object files, clearly named like MD2.o MD5.o SHA1.o, ...). Thanks in advance, Sebastian