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 schri
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
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
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 d
On 07/04/11 05:35 PM, 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
On 07.04.2011, at 23:35, 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 compa
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
On Mon, Apr 4, 2011 at 6:13 PM, Michael Walle wrote:
> Hi Benjamin,
>
>> Let me know if you need more info.
>
> what happens if you configure with
>
> ./configure --target-list=x86_64-softmmu --disable-opengl
>
Works as usual.
The problem I'm facing stems from linking to libGL and memory
protecti
Hi Benjamin,
> Let me know if you need more info.
what happens if you configure with
./configure --target-list=x86_64-softmmu --disable-opengl
--
Michael
