From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Fedora Core 2 patch
Date: Thu, 24 Jun 2004 16:55:10 +0600 [thread overview]
Message-ID: <40DAB30E.10605@ums.usu.ru> (raw)
In-Reply-To: <200406241231.43037.hetz@softier.com>
Hetz Ben Hamo wrote:
> I'm removing the patch for fedora.
>
> The solution is simple. instead of just running qemu and sticking the
> parameters, you should do:
>
> LD_ASSUME_KERNEL=2.2.5 qemu <and the qemu parameters>
>
> Feel free to create an alias in your .bashrc or whatever you favorite shell
> is ;)
>
> I tested it on Fedora Core 2 and in Rawhide - works perfectly OK.
Unfortunately, this solution is not acceptable for me. The problem is
that it relies upon RedHat-specific glibc setup.
RedHat provides separate glibc libraries for TLS and (obsolete) non-TLS
systems. The LD_ASSUME_KERNEL variable selects between them and forces
qemu to use the old library.
On my system (LFS CVS HEAD as of April 2004) there is just NO non-TLS
version of glibc, so this "solution" doesn't work. The same applies to
most of modern source-based distros (e.g. Gentoo).
Probably we have to insert into the ./configure script a test for the
brokenness that forces us to use __libc_sigaction on older systems, and
use __libc_sigaction ONLY if the regular sigaction is broken.
Unfortunately, I can't do this myself because I don't know what exactly
is broken and therefore I can't write the testcase.
Yes, this means that there will be no single portable binary
distribution. But it is not worse than the current situation with
non-working qemu binary.
--
Alexander E. Patrakov
next prev parent reply other threads:[~2004-06-24 11:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 9:14 [Qemu-devel] Fedora Core 2 patch Jean-Michel POURE
2004-06-24 9:31 ` Hetz Ben Hamo
2004-06-24 10:55 ` Alexander E. Patrakov [this message]
2004-06-24 10:26 ` Jean-Michel POURE
2004-06-24 11:53 ` Hetz Ben Hamo
2004-06-24 12:17 ` [Qemu-devel] Fedora Core 2 as guest OS Fabrice Bellard
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=40DAB30E.10605@ums.usu.ru \
--to=patrakov@ums.usu.ru \
--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).