From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Cc: guillem@debian.org
Subject: Re: [Qemu-devel] ROM sources and checkout dates or versions
Date: Thu, 23 Dec 2004 23:26:12 +0100 [thread overview]
Message-ID: <41CB4604.3030008@bellard.org> (raw)
In-Reply-To: <20041223134038.GD776@zulo.hadrons.org>
Guillem Jover wrote:
> Hi,
>
> We've a problem packaging current qemu sources for Debian, as they
> contain binaries without sources (namely the roms), thus forcing us
> to repackage the upstream tarball to remove them. Also due to that,
> we've started depending on an external package providing the Bochs
> bios binary, but then now we have some problems with the emulated
> network card. See for example:
>
> <http://bugs.debian.org/285752>
> <http://bugs.debian.org/284132>
>
> I'd like to know if it would be possible to include the sources for
> those roms, so we can easily reproduce the same binaries from source,
> and be able to use the pristine source tarball as well. Otherwise
> having the checkout dates or exact version used would be of help,
> although a bit cumbersome.
Hi,
It is a bad idea to use the BIOSes from Bochs because QEMU has specific
patches. Moreover, the recent Bochs BIOS may be incompatible with QEMU
(I need to look at them). You should include the QEMU BIOSes as-is in an
architecture independent Debian package.
I am relunctant to provide the source code because it would duplicate
the code from Bochs and it would need a build process I am not ready to
support. The provided diffs are suffisant to build the BIOS because they
give the date and CVS version of the corresponding Bochs code.
Fabrice.
next prev parent reply other threads:[~2004-12-23 22:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-23 13:40 [Qemu-devel] ROM sources and checkout dates or versions Guillem Jover
2004-12-23 22:26 ` Fabrice Bellard [this message]
2004-12-24 10:08 ` Guillem Jover
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=41CB4604.3030008@bellard.org \
--to=fabrice@bellard.org \
--cc=guillem@debian.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).