All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steffen Liebergeld <usenet@gmx.eu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Cross compiling qemu for ARM
Date: Fri, 28 Nov 2008 10:13:25 +0000 (UTC)	[thread overview]
Message-ID: <ggog85$nk$1@ger.gmane.org> (raw)

Hi,

I'm trying to get Qemu 0.9.1 cross compiled for the ARM platform.

I have been using these configure flags:
--target-list=arm-softmmu
--source-path=$HOME/Source/qemu-0.9.1/
--cross-prefix=arm-linux-
--static
--host-cc=/usr/bin/gcc-3.4
--prefix=$HOME/Binary/qemu/
--disable-linux-user
--disable-darwin-user
--disable-sdl
--disable-gfx-check

I have the complete arm crosscompiling toolchain including crosscompilers and
libs like zlib. (Unfortunatly I didn't find an option to give paths to zlib
headers and lib, so I set them manually. Do you know an easy way to set them?)

Compiling goes well until dyngen tries to execute:
make[1]: Entering directory `/home/s1010824/Build/arm/qemu/arm-softmmu'
../dyngen -o op.h op.o
dyngen: op_movl_T0_r0, 8: function too small
make[1]: *** [op.h] Error 1
make[1]: Leaving directory `/home/s1010824/Build/arm/qemu/arm-softmmu'

Do you have an idea how I can fix that? Did you do cross compilation of qemu
yourself and know good documention about it?

Thank you in advance,
Steffen Liebergeld

             reply	other threads:[~2008-11-28 10:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-28 10:13 Steffen Liebergeld [this message]
2008-11-28 11:55 ` [Qemu-devel] Re: Cross compiling qemu for ARM Steffen Liebergeld
2008-11-28 12:07   ` Laurent Desnogues
2008-11-28 13:09     ` Steffen Liebergeld
2008-11-28 13:21       ` Laurent Desnogues
2008-11-28 13:27 ` [Qemu-devel] " Paul Brook
2008-11-28 14:58   ` [Qemu-devel] " Steffen Liebergeld
2008-11-30  3:01     ` andrzej zaborowski

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='ggog85$nk$1@ger.gmane.org' \
    --to=usenet@gmx.eu \
    --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.