From: Michael Walle <michael@walle.cc>
To: Benjamin Poirier <benjamin.poirier@gmail.com>
Cc: blauwirbel@gmail.com,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: [Qemu-devel] Re: [regression] configure: add opengl detection
Date: Thu, 7 Apr 2011 23:35:47 +0200 [thread overview]
Message-ID: <201104072335.47660.michael@walle.cc> (raw)
In-Reply-To: <BANLkTim+z2cfg2q+2U=g0+rQi-F-KHP3kw@mail.gmail.com>
Am Mittwoch 06 April 2011, 16:13:58 schrieb Benjamin Poirier:
> Works as usual.
> The problem I'm facing stems from linking to libGL and memory
> protection issues. The particular system I ran this on has the binary
> nvidia driver and its companion libGL.so.260.19.44. As such I'd take
> no offense if we wave it off as a "problem in the unsupported binary
> drivers" and I'll be satisfied configuring with no opengl on that
> system.
I would also be happy with opengl disabled by default. It is only used for one
hardware model (milkymist-tmu2.c) atm. I don't think its worth that this
potentially breaks qemu for lots of users. What do you think?
--
Michael
next prev parent reply other threads:[~2011-04-07 21:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 12:04 [Qemu-devel] [regression] configure: add opengl detection Benjamin Poirier
2011-04-04 18:13 ` [Qemu-devel] " Michael Walle
2011-04-06 14:13 ` Benjamin Poirier
2011-04-07 21:35 ` Michael Walle [this message]
2011-04-07 22:38 ` Alexander Graf
2011-04-07 22:38 ` Benjamin Poirier
2011-04-08 10:00 ` Edgar E. Iglesias
2011-04-08 21:13 ` Michael Walle
2011-04-09 0:04 ` Alexander Graf
2011-04-09 4:20 ` Edgar E. Iglesias
2011-04-09 21:13 ` [Qemu-devel] [PATCH] configure: disable opengl per default Michael Walle
2011-04-10 7:34 ` [Qemu-devel] " Jan Kiszka
2011-04-12 21:34 ` [Qemu-devel] " Aurelien Jarno
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=201104072335.47660.michael@walle.cc \
--to=michael@walle.cc \
--cc=agraf@suse.de \
--cc=benjamin.poirier@gmail.com \
--cc=blauwirbel@gmail.com \
--cc=edgar.iglesias@gmail.com \
--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).