From: Thiemo Seufer <ths@networkno.de>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>
Subject: [Qemu-devel] sparc-linux-user fails to build on Linux/ppc
Date: Tue, 27 Nov 2007 10:54:40 +0000 [thread overview]
Message-ID: <20071127105440.GA31551@networkno.de> (raw)
Some recent change broke compilation of sparc-linux-user on
Linux/ppc.
Thiemo
make -C i386-linux-user all
make[1]: Entering directory `/home/ths/qemu/qemu-work/i386-linux-user'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/ths/qemu/qemu-work/i386-linux-user'
make -C arm-linux-user all
make[1]: Entering directory `/home/ths/qemu/qemu-work/arm-linux-user'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/ths/qemu/qemu-work/arm-linux-user'
make -C armeb-linux-user all
make[1]: Entering directory `/home/ths/qemu/qemu-work/armeb-linux-user'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/home/ths/qemu/qemu-work/armeb-linux-user'
make -C sparc-linux-user all
make[1]: Entering directory `/home/ths/qemu/qemu-work/sparc-linux-user'
gcc-3.4 -g -Wl,-T,/home/ths/qemu/qemu-work/ppc.ld -o qemu-sparc main.o syscall.o strace.o mmap.o signal.o path.o osdep.o thunk.o elfload.o linuxload.o uaccess.o libqemu.a gdbstub.o -lm -lrt -lpthread
libqemu.a(translate-op.o): In function `dyngen_code':
/home/ths/qemu/qemu-work/sparc-linux-user/./op.h:5035: undefined reference to `do_fitoq'
/home/ths/qemu/qemu-work/sparc-linux-user/./op.h:5035: undefined reference to `do_fitoq'
libqemu.a(op.o): In function `op_fitoq':
/home/ths/qemu/qemu-work/target-sparc/op.c:1806: undefined reference to `do_fitoq'
collect2: ld returned 1 exit status
make[1]: *** [qemu-sparc] Error 1
make[1]: Leaving directory `/home/ths/qemu/qemu-work/sparc-linux-user'
make: *** [subdir-sparc-linux-user] Error 2
reply other threads:[~2007-11-27 10:54 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=20071127105440.GA31551@networkno.de \
--to=ths@networkno.de \
--cc=blauwirbel@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).