From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] SIGSEGV on start of qemu-fast under gentoo
Date: Wed, 07 Apr 2004 22:13:16 +0200 [thread overview]
Message-ID: <407460DC.5090104@bellard.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0404071959210.28291@alpha.polcom.net>
Hi,
It is totally _wrong_ to compile qemu-fast with a -shared option. If I
used a static build there was certainly a reason :-) So you should
better not compile qemu-fast if your distribution has not the right
packages, as it it said in the (new) QEMU FAQ...
Fabrice.
Grzegorz Kulewski wrote:
> Hi,
>
> I managed to compile QEMU under gentoo using qemu-cvs-1.3.ebuild with this
> command at the end:
>
> gcc -static -Wl,-T,../i386-vl.ld -o qemu-fast vl.o osdep.o block.o
> monitor.o ide.o ne2000.o pckbd.o vga.o sb16.o dma.o oss.o fdc.o
> mc146818rtc.o serial.o i8259.o i8254.o pc.o gdbstub.o sdl.o libqemu.a
> -shared -lm -L/usr/lib -Wl,-rpath,/usr/lib -lSDL -lpthread -lm -ldl
> -lasound -L/usr/X11R6/lib -lX11 -lXext -laa -L/usr/lib -Wl,-rpath,/usr/lib
> -laa -lm -L/usr/X11R6/lib -lX11 -lncurses -lutil
>
> And I get immendiate SIGSEGV when trying to launch such created qemu-fast.
>
> What I am doing wrong???
>
>
> thanks in advance
>
> Grzegorz
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/qemu-devel
>
next prev parent reply other threads:[~2004-04-07 20:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 20:11 [Qemu-devel] Gentoo & qemu & non-static build rutger
2004-04-04 20:27 ` Jim C. Brown
2004-04-05 18:19 ` Carlos Valiente
2004-04-07 18:04 ` [Qemu-devel] SIGSEGV on start of qemu-fast under gentoo Grzegorz Kulewski
2004-04-07 20:13 ` Fabrice Bellard [this message]
2004-04-06 20:23 ` [Qemu-devel] Gentoo & qemu & non-static build rutger
2004-04-15 19:21 ` [Qemu-devel] [PATCH] /dev/tun support (was: Re: Gentoo & qemu & non-static build) Gabriel Ebner
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=407460DC.5090104@bellard.org \
--to=fabrice@bellard.org \
--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.