qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Alexander Graf <agraf@suse.de>
Cc: blauwirbel@gmail.com,
	Benjamin Poirier <benjamin.poirier@gmail.com>,
	Michael Walle <michael@walle.cc>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [regression] configure: add opengl detection
Date: Sat, 9 Apr 2011 06:20:48 +0200	[thread overview]
Message-ID: <20110409042048.GB26363@laped.lan> (raw)
In-Reply-To: <77D418C9-CD2D-4CD5-AEA5-E7A4CD15E237@suse.de>

On Sat, Apr 09, 2011 at 02:04:07AM +0200, Alexander Graf wrote:
> 
> On 08.04.2011, at 23:13, Michael Walle wrote:
> 
> > Am Freitag 08 April 2011, 12:00:32 schrieb Edgar E. Iglesias:
> >> On Thu, Apr 07, 2011 at 11:35:47PM +0200, Michael Walle wrote:
> >>> 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?
> >> 
> >> I agree, FWIW I've already got a couple of reports regarding the same
> >> problem.
> >> 
> >> Cheers
> > 
> > OTOH, a milkymist team member is worried that distributions would just build 
> > the QEMU package with the default options and all will ship qemu-system-lm32 
> > without opengl.
> > 
> > What do you think about disabling opengl by default except for lm32 targets?
> 
> I would really like to see some more logic behind target library requirements and actual linking anyway. On PPC for example, we link with libfdt to do device tree modifications, but link with libfdt on x86 as well when it's detected. Same goes for the xen libraries.
> 
> Being more clever about target requirements would certainly be useful. For now, I'd disable OpenGL by default though and then follow up with a patch to add the cleverness :).

Yep, that sounds good.

Cheers

  reply	other threads:[~2011-04-09  4:25 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
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 [this message]
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=20110409042048.GB26363@laped.lan \
    --to=edgar.iglesias@gmail.com \
    --cc=agraf@suse.de \
    --cc=benjamin.poirier@gmail.com \
    --cc=blauwirbel@gmail.com \
    --cc=michael@walle.cc \
    --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).