From: "Philipp Gühring" <pg@futureware.at>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] x86_64 vs. i386
Date: Mon, 31 Jul 2006 10:58:46 -0000 [thread overview]
Message-ID: <200607311258.48456.pg@futureware.at> (raw)
Hi,
The current Linux distributions for x86_64 can run both 64Bit and 32Bit
applications. But they have one major problem: 64Bit applications have to use
64Bit libraries, and 32Bit applications have to use 32Bit libraries.
One huge problem for example is the non-existance of a 64Bit Flash-Player at
the moment.
Those are the usual error message for 32 vs. 64 bit problems
/usr/lib/firefox/firefox-bin: error while loading shared libraries:
libasound.so.2: wrong ELF class: ELFCLASS64
Inconsistency detected by ld.so: dl-close.c: 342: _dl_close: Assertion
`tmap->l_ns == ns' failed!
Now I am wondering, whether it would be possible to integrate the processor
emulator of qemu into the Linux kernel, so that applications can
transparently use different-bitsized libraries by qemulating them on demand?
Best regards,
Philipp Gühring
next reply other threads:[~2006-07-31 10:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 10:58 Philipp Gühring [this message]
2006-08-20 18:38 ` [Qemu-devel] x86_64 vs. i386 Thomas Steffen
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=200607311258.48456.pg@futureware.at \
--to=pg@futureware.at \
--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).