From: "Jim C. Brown" <jma5@umd.edu>
To: esrever_otua@pythonhacker.is-a-geek.net, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Remove qemu-fast warning
Date: Mon, 28 Feb 2005 18:05:57 -0500 [thread overview]
Message-ID: <20050228230557.GA13037@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <1109627846.15140.2.camel@localhost.localdomain>
On Tue, Mar 01, 2005 at 10:57:26AM +1300, Darryl Dixon wrote:
> Incidentally to this, I discovered that qemu will both ./configure (with
> --target-list=i386-softmmu) and make && make install fine with no
> sdl-devel installed, and will run fine, but will not have any graphical
> output. I assume that this is technically a bug, as it doesn't warn at
> any point that this will be the case.
>
> Cheers,
> D
>
The bug would be that it doesn't warn. It should state that there will be no
graphical output if it can't find libsdl-devel. (Tho you should have gotten
a warning that SDL was not detected period.)
Does this bug occur w/o Paul Brooks patch as well?
qemu needs libsdl-devel in order to compile correctly and link to the libsdl
library, in case that was not made clear before.
> On Mon, 2005-02-28 at 21:07 +0000, Paul Brook wrote:
>
> >The attached patch removes the warning about lack of static SDL. This is only
> >userd by qemu-fast, which isn't build by default. Anyone building qemu-fast
> >should know what they're doing anyway. The current warning just confuses
> >people.
> >
> >Please apply.
> >
> >Paul
> >_______________________________________________
> >Qemu-devel mailing list
> >Qemu-devel@nongnu.org
> >http://lists.nongnu.org/mailman/listinfo/qemu-devel
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2005-02-28 23:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 21:07 [Qemu-devel] Remove qemu-fast warning Paul Brook
2005-02-28 21:57 ` Darryl Dixon
2005-02-28 23:05 ` Jim C. Brown [this message]
2005-03-01 2:06 ` Darryl Dixon
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=20050228230557.GA13037@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--cc=esrever_otua@pythonhacker.is-a-geek.net \
--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).