From: Martin Mohring <martin.mohring@opensuse.org>
To: qemu-devel@nongnu.org
Cc: Jan Kiszka <jan.kiszka@siemens.com>
Subject: [Qemu-devel] openSUSE: Build Service 1.5 Beta 1 release
Date: Mon, 01 Dec 2008 19:25:45 +0100 [thread overview]
Message-ID: <49342C29.1090003@opensuse.org> (raw)
In-Reply-To: <E7117B3D-BF13-4D8F-97DF-21289F196B20@handhelds.org>
Hi,
We have been working hard and testing like mad, now its official: OBS
1.5 beta is out:
http://lists.opensuse.org/opensuse-buildservice/2008-12/msg00011.html
For the Cross Development support, we are currently using some fixed
qemu svn snapshot based on svn trunk -r 5828 and later. We try both tcg
version with new gcc compilers up to 4.3 and also old code generator
with old gcc 3 compiler. We specifically use and test QEMU User Mode due
to performance considerations.
For you it might be of special interest that we have Debian/Ubuntu @ ARM
already working with this release.
Tnx for your great work.
Martin Mohring
OBS Maintainer / opensuse.org
parent reply other threads:[~2008-12-01 18:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E7117B3D-BF13-4D8F-97DF-21289F196B20@handhelds.org>]
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=49342C29.1090003@opensuse.org \
--to=martin.mohring@opensuse.org \
--cc=jan.kiszka@siemens.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 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).