From: iQQator <subach.pavel@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1568589] Re: Compile for os x host failed
Date: Sun, 10 Apr 2016 19:50:29 -0000 [thread overview]
Message-ID: <20160410195029.4163.32916.malone@gac.canonical.com> (raw)
In-Reply-To: 20160410192014.3685.18953.malonedeb@gac.canonical.com
Also for i386
LINK i386-softmmu/qemu-system-i386
Undefined symbols for architecture x86_64:
"_event_notifier_init_fd", referenced from:
_process_msg in ivshmem.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [qemu-system-i386] Error 1
make: *** [subdir-i386-softmmu] Error 2
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1568589
Title:
Compile for os x host failed
Status in QEMU:
New
Bug description:
Hello QEMU,
I try compile qemu from git pulled by me today and have a troubles:
GEN trace/generated-helpers.c
CC aarch64-softmmu/trace/generated-helpers.o
LINK aarch64-softmmu/qemu-system-aarch64
Undefined symbols for architecture x86_64:
"_event_notifier_init_fd", referenced from:
_process_msg in ivshmem.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [qemu-system-aarch64] Error 1
make: *** [subdir-aarch64-softmmu] Error 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1568589/+subscriptions
next prev parent reply other threads:[~2016-04-10 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-10 19:20 [Qemu-devel] [Bug 1568589] [NEW] Compile for os x host failed iQQator
2016-04-10 19:29 ` [Qemu-devel] [Bug 1568589] " iQQator
2016-04-10 19:50 ` iQQator [this message]
2016-04-10 20:05 ` iQQator
2016-04-11 6:49 ` Markus Armbruster
2016-06-13 8:46 ` T. Huth
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=20160410195029.4163.32916.malone@gac.canonical.com \
--to=subach.pavel@gmail.com \
--cc=1568589@bugs.launchpad.net \
--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).