All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jocelyn Mayer <l_indien@magic.fr>
To: qemu mailing list <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] SDL, GLIBC_PRIVATE error for __libc_sigaction
Date: 13 Jul 2004 14:30:30 +0200	[thread overview]
Message-ID: <1089721828.29394.228.camel@jma1.dev.netgem.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0407131223500.4661@fogarty.jakma.org>

On Tue, 2004-07-13 at 13:27, Paul Jakma wrote:
> On Wed, 14 Jul 2004, Hetz Ben Hamo wrote:
> 
> > Do: LD_ASSUME_KERNEL=2.2.5 qemu <and the qemu parameters>
> 
> Hmm, that doesnt work:
> 
>   LD_ASSUME_KERNEL=2.2.5 ./i386-softmmu/qemu -hda /mnt/s10/hda.img -hdb /mnt/s10/hdb.img -m 256
> ./i386-softmmu/qemu: error while loading shared libraries: libm.so.6: 
> cannot open shared object file: No such file or directory
> 
> What I have done is just to remove the sigaction stuff from vl.c, as 
> I found a post to the list (via google) which suggested that this 
> libc abuse is only needed for old libc's (linuxthreads?). If I do 
> that qemu works, I get a window popped up, it stays black and after a 
> while qemu segfaults. Thing is, qemu also segfaults if i compile 
> without SDL support.
> 
> This is on x86-64. Is qemu known to work on 64bit systems? I noticed 
> quite a few integer<->pointer warnings when compiling qemu..

I don't use qemu pc emulation a lot, but qemu-ppc runs fine on my
x86_64, with a Gentoo distrib, using Linux kernel 2.6.
I had some issues with PC emulation last time I tried it:
the BIOS seemed to start to execute then freezed.
But it's been quite a long time ago...
I'll retry and tell here if it's better now.

-- 
Jocelyn Mayer <l_indien@magic.fr>
Never organized

  reply	other threads:[~2004-07-13 12:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-12 19:13 [Qemu-devel] SDL, GLIBC_PRIVATE error for __libc_sigaction Paul Jakma
2004-07-13 21:34 ` Hetz Ben Hamo
2004-07-13 11:27   ` Paul Jakma
2004-07-13 12:30     ` Jocelyn Mayer [this message]
2004-07-13 13:36       ` Martin Garton
2004-07-13 12:53     ` Paul Jakma
2004-07-13 13:23       ` Frederic Bezies
2004-07-13 13:33         ` Hetz Ben Hamo

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=1089721828.29394.228.camel@jma1.dev.netgem.com \
    --to=l_indien@magic.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.