From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=46586 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PUPRH-0004dr-Px
	for qemu-devel@nongnu.org; Sun, 19 Dec 2010 15:01:10 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <stefboombastic@gmail.com>) id 1PUPR6-00024u-NL
	for qemu-devel@nongnu.org; Sun, 19 Dec 2010 15:00:53 -0500
Received: from mail-ww0-f53.google.com ([74.125.82.53]:54827)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefboombastic@gmail.com>) id 1PUPR6-00024j-JC
	for qemu-devel@nongnu.org; Sun, 19 Dec 2010 15:00:52 -0500
Received: by wwi18 with SMTP id 18so2309268wwi.10
	for <qemu-devel@nongnu.org>; Sun, 19 Dec 2010 12:00:51 -0800 (PST)
Message-ID: <4D0E6470.3070408@gmail.com>
Date: Sun, 19 Dec 2010 21:00:48 +0100
From: Stefano Bonifazi <stefboombastic@gmail.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] libqemu.a not made with version 0.13
References: <4D0E16B6.6040201@gmail.com>
	<AANLkTim3FCA3fiAsX4eo_BpYQGrp0B=zHxwsAatd_znz@mail.gmail.com>
	<E3D3C7A2-E812-4323-ABBA-A47043A69256@web.de>
In-Reply-To: <E3D3C7A2-E812-4323-ABBA-A47043A69256@web.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: =?ISO-8859-1?Q?Andreas_F=E4rber?= <andreas.faerber@web.de>
Cc: Blue Swirl <blauwirbel@gmail.com>, QEMU Developers <qemu-devel@nongnu.org>

On 12/19/2010 06:03 PM, Andreas Färber wrote:
> In particular, on some platforms libqemu.a would seem to compile okay 
> but the resulting QEMU executable would simply crash. We got around 
> these --whole-archive issues by putting together lists of object files 
> in Makefile.objs et al. that we can link into QEMU's executables 
> directly.
>
> It is theoretically possible for your application to integrate with 
> our Makefiles and link to such objects directly. But again this is not 
> supported and may break at any time. If you just need it for one 
> assignment it may work - but don't expect instructions, you'd probably 
> be the first one trying!
>
> Regards,
> Andreas
Thank You for your warnings!
I am just a student, it is already very hard for me to understand all 
the mechanisms of QEMU.. I can't base my project on bugged sources, I 
would be not able of fixing them while developing my project upon them..
Any idea how to go on?
Maybe editing qemu-ppc, inserting inside my own code?
Thank you in advance!
Stefano B.