From: Oliver Gerlich <olig9@gmx.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Qemu with wxWidgets: g++ errors, ABI mismatch
Date: Sat, 24 Jun 2006 00:58:32 +0200 [thread overview]
Message-ID: <449C7218.7060300@gmx.de> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
while playing with wxWidgets and Qemu, I noticed several problems and
hoped that you know a solution for this.
I added a single C++ source file (wxgui.cpp) for wxWidgets stuff, which
in turn includes vl.h . wxgui.cpp is compiled with g++ (tried 3.3 and
4.0), but that compiler gives some warnings about cpu-all.h, like this:
../cpu-all.h: In function ?uint64_t ldq_be_p(void*)?:
../cpu-all.h:419: error: pointer of type ?void *? used in arithmetic
Is there a solution other than casting ptr to uint8_t* and then back to
void* in the offending line?
Another more serious thing is that the wxWidgets libs on Debian
Testing/Unstable seem to be compiled with gcc 4.0 (this is probably the
case on other distros as well), while Qemu is compiled with gcc 3.3.
This leads to a runtime error:
$ i386-softmmu/qemu -cdrom /mnt/hda5/ubuntu.iso -boot d
Fatal Error: Mismatch between the program and library build versions
detected.
The library used 2.6 (no debug,Unicode,compiler with C++ ABI 1002,wx
containers,compatible with 2.4),
and your program used 2.6 (no debug,Unicode,compiler with C++ ABI 102,wx
containers,compatible with 2.4).
Aborted
Is there a way around this problem? Probably wxWidgets doesn't like the
different ABIs in gcc 3.3 and 4.0, but maybe some clever linking could
work around this? Any hints?
Thanks,
Oliver
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEnHIWTFOM6DcNJ6cRAmBtAKC05oTBZaPGgFZ9d4PkrSbsn2pt7QCfQK6t
+N3SSzz4ev5x+IF/9BAupY8=
=V8zh
-----END PGP SIGNATURE-----
reply other threads:[~2006-06-23 22:58 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=449C7218.7060300@gmx.de \
--to=olig9@gmx.de \
--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).