From: David Barrett <dbarrett@quinthar.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Compiling with 3.3 on Ubuntu-based system
Date: Wed, 02 Apr 2008 20:11:27 -0700 [thread overview]
Message-ID: <47F44ADF.90500@quinthar.com> (raw)
Ok, so next up is trying it on a couple other servers. I've already
tried the crazy 2.4/2.6 bastard with an ancient gcc, but I'm giving up
on that one.
Next up I'm going to try an Ubuntu-based server. Both gcc 4 and 3.3 are
installed, but /usr/bin/gcc is linked to 3.3:
rs@a69-26-190-189:/usr/bin$ ls -latr /usr/bin/gcc
lrwxrwxrwx 1 root root 7 Apr 3 01:35 /usr/bin/gcc -> gcc-3.3
rs@a69-26-190-189:/tmp/qemu-0.9.1$ gcc -v
Reading specs from /usr/lib/gcc-lib/i486-linux-gnu/3.3.6/specs
Configured with: ../src/configure -v --enable-languages=c,c++,ada
--prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info
--with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared
--enable-__cxa_atexit --with-system-zlib --enable-nls
--without-included-gettext --enable-clocale=gnu --enable-debug
i486-linux-gnu
Thread model: posix
gcc version 3.3.6 (Ubuntu 1:3.3.6-10)
rs@a69-26-190-189:/tmp/qemu-0.9.1$
When I ./configure it warns about a lack of SDL headers, but I think I
remember hearing this can be safely ignored. (?) Furthermore, it seems
to compile fine for a while, but then gets stuck here:
rs@a69-26-190-189:/tmp/qemu-0.9.1$ make
make -C i386-linux-user all
make[1]: Entering directory `/tmp/qemu-0.9.1/i386-linux-user'
../dyngen -c -o opc.h op.o
dyngen: Unsupported ELF class
make[1]: *** [opc.h] Error 1
make[1]: Leaving directory `/tmp/qemu-0.9.1/i386-linux-user'
make: *** [subdir-i386-linux-user] Error 2
Alas, so close. Any suggestions?
I'm going to try compiling this on my Ubuntu laptop to make sure it
works there (I've been using the pre-compiled binaries). Then I'm going
to try a newer CVS snapshot (but
http://qemu-forum.ipi.fi/qemu-snapshots/ seems to be down). If I can
only get it working on one of these servers I'll be in nirvana!
-david
reply other threads:[~2008-04-03 3:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=47F44ADF.90500@quinthar.com \
--to=dbarrett@quinthar.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.