From: Sunil Amitkumar Janki <psychicistnonconformist@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] QEMU build error on MIPS
Date: Thu, 31 May 2007 16:53:47 +0200 [thread overview]
Message-ID: <465EE17B.2090905@gmail.com> (raw)
I am running Slackware Current on MIPS (Loongson) and am trying
to compile QEMU with GCC 3.4.6 using Glibc 2.5 and 2.6.18.1 kernel
headers. The build works fine except for warnings about linking PIC
code with no-PIC code but I get this error message when building Alpha
user emulation:
> make[1]: Entering directory `/tmp/qemu-20070531/alpha-linux-user'
> gcc -O2 -march=r4600 -Wall -O2 -g -fno-strict-aliasing -I. -I..
> -I/tmp/qemu-20070531/target-alpha -I/tmp/qemu-20070531
> -I/tmp/qemu-20070531/linux-user -I/tmp/qemu-20070531/linux-user/alpha
> -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
> -I/tmp/qemu-20070531/fpu -I/tmp/qemu-20070531/slirp -c -o main.o
> /tmp/qemu-20070531/linux-user/main.c
> gcc -O2 -march=r4600 -Wall -O2 -g -fno-strict-aliasing -I. -I..
> -I/tmp/qemu-20070531/target-alpha -I/tmp/qemu-20070531
> -I/tmp/qemu-20070531/linux-user -I/tmp/qemu-20070531/linux-user/alpha
> -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
> -I/tmp/qemu-20070531/fpu -I/tmp/qemu-20070531/slirp -c -o syscall.o
> /tmp/qemu-20070531/linux-user/syscall.c
> In file included from /tmp/qemu-20070531/linux-user/syscall_defs.h:850,
> from /tmp/qemu-20070531/linux-user/qemu.h:8,
> from /tmp/qemu-20070531/linux-user/syscall.c:72:
> /tmp/qemu-20070531/linux-user/alpha/termbits.h:2: error: conflicting
> types for 'speed_t'
> /usr/include/asm/termbits.h:17: error: previous declaration of
> 'speed_t' was here
> /tmp/qemu-20070531/linux-user/alpha/termbits.h:3: error: conflicting
> types for 'tcflag_t'
> /usr/include/asm/termbits.h:18: error: previous declaration of
> 'tcflag_t' was here
> /tmp/qemu-20070531/linux-user/syscall.c: In function
> `target_to_host_cmsg':
> /tmp/qemu-20070531/linux-user/syscall.c:438: warning: cast to pointer
> from integer of different size
> /tmp/qemu-20070531/linux-user/syscall.c: In function
> `host_to_target_cmsg':
> /tmp/qemu-20070531/linux-user/syscall.c:483: warning: cast to pointer
> from integer of different size
> /tmp/qemu-20070531/linux-user/syscall.c:3314:2: warning: #warning not
> supported
> /tmp/qemu-20070531/linux-user/syscall.c: At top level:
> /tmp/qemu-20070531/linux-user/syscall.c:957: warning: 'do_socketcall'
> defined but not used
> /tmp/qemu-20070531/linux-user/syscall.c:1135: warning: 'do_ipc'
> defined but not used
Since I am one of the people requesting Alpha user/system emulation I
wouldn't mind
helping to maintain Alpha user emulation and maybe even contribute to
Alpha system
emulation. The only thing is that I am very new to QEMU and still don't
understand
all of its internals. But I'm willing to learn by trial and error and
some RTFMing.
To that end I have over the last few weeks read through the Alpha
documentation
that I was pointed to by Wikipedia. I am also dabbling with MIPS on the
Lemote Fu
Long box and reading through HPPA documentation so I hope that this will
enable
me to much better understand the various RISC architectures and how to
implement
them in QEMU.
Sunil Janki
next reply other threads:[~2007-05-31 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 14:53 Sunil Amitkumar Janki [this message]
2007-05-31 15:26 ` [Qemu-devel] QEMU build error on MIPS Thiemo Seufer
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=465EE17B.2090905@gmail.com \
--to=psychicistnonconformist@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 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).