From: Stefano Bonifazi <stefboombastic@gmail.com>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: Blue Swirl <blauwirbel@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] libqemu.a not made with version 0.13
Date: Sun, 19 Dec 2010 21:00:48 +0100 [thread overview]
Message-ID: <4D0E6470.3070408@gmail.com> (raw)
In-Reply-To: <E3D3C7A2-E812-4323-ABBA-A47043A69256@web.de>
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.
prev parent reply other threads:[~2010-12-19 20:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-19 14:29 [Qemu-devel] libqemu.a not made with version 0.13 Stefano Bonifazi
2010-12-19 16:10 ` Blue Swirl
2010-12-19 16:32 ` Stefano Bonifazi
2010-12-19 16:51 ` Andreas Färber
2010-12-19 19:53 ` Stefano Bonifazi
2010-12-20 18:31 ` Blue Swirl
2010-12-21 9:07 ` Stefano Bonifazi
2010-12-19 17:03 ` Andreas Färber
2010-12-19 20:00 ` Stefano Bonifazi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D0E6470.3070408@gmail.com \
--to=stefboombastic@gmail.com \
--cc=andreas.faerber@web.de \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.