remove the configure arugument named --enable-opengl.<br><br><div class="gmail_quote">2011/2/21 <span dir="ltr"><<a href="mailto:spice-devel-request@lists.freedesktop.org">spice-devel-request@lists.freedesktop.org</a>></span><br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Send Spice-devel mailing list submissions to<br>
<a href="mailto:spice-devel@lists.freedesktop.org">spice-devel@lists.freedesktop.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.freedesktop.org/mailman/listinfo/spice-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/spice-devel</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:spice-devel-request@lists.freedesktop.org">spice-devel-request@lists.freedesktop.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:spice-devel-owner@lists.freedesktop.org">spice-devel-owner@lists.freedesktop.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Spice-devel digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. help for spice-0.6.3 (???)<br>
2. testing the spice protocol (Bill Sanford)<br>
3. Re: [PATCH] protocol: RFC: add common channel caps for AUTH<br>
mechanism selection (Alon Levy)<br>
4. Re: help for spice-0.6.3 (Hans de Goede)<br>
5. Re: testing the spice protocol (Alon Levy)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sat, 12 Feb 2011 14:17:30 +0800 (CST)<br>
From: ??? <<a href="mailto:purifyspray@126.com">purifyspray@126.com</a>><br>
Subject: [Spice-devel] help for spice-0.6.3<br>
To: <a href="mailto:spice-devel@lists.freedesktop.org">spice-devel@lists.freedesktop.org</a><br>
Message-ID: <<a href="mailto:f936ee.7c04.12e18845c3f.Coremail.purifyspray@126.com">f936ee.7c04.12e18845c3f.Coremail.purifyspray@126.com</a>><br>
Content-Type: text/plain; charset="gbk"<br>
<br>
hello?<br>
I have download the spice-0.6.3.tar.bz2 fromhttp://<a href="http://www.spice-space.org" target="_blank">www.spice-space.org</a><br>
When i compile and install spice, I have encountered some problem, I need some<br>
help ,Thanks<br>
The command "configure" have passed , no problem,but in compile process ,there is some mistakes<br>
The following descibe the situation<br>
./configure --includedir=/usr/include --libdir=/usr/lib64 --enable-opengl --enable-gui<br>
Spice 0.6.3<br>
==============<br>
prefix: /usr/local<br>
c compiler: gcc<br>
c++ compiler: g++<br>
Have XRANDR 1.2: yes<br>
Support tunneling: no<br>
Red target: x11<br>
OpenGL: yes<br>
GUI: yes<br>
Now type 'make' to build spice<br>
<br>
<br>
make<br>
<br>
red_window.cpp: In member function ?__GLXcontextRec* RedWindow::create_context_gl()?:<br>
red_window.cpp:2050: error: cannot convert ?__GLXcontextRec*? to ?__GLXcontextRec**? in assignment<br>
red_window.cpp:2053: error: cannot convert ?__GLXcontextRec**? to ?__GLXcontextRec*? in return<br>
make[5]: *** [red_window.o] Error 1<br>
make[5]: Leaving directory `/tmp/spice-0.6.3/client/x11'<br>
make[4]: *** [all-recursive] Error 1<br>
make[4]: Leaving directory `/tmp/spice-0.6.3/client/x11'<br>
make[3]: *** [all-recursive] Error 1<br>
make[3]: Leaving directory `/tmp/spice-0.6.3/client'<br>
make[2]: *** [all] Error 2<br>
make[2]: Leaving directory `/tmp/spice-0.6.3/client'<br>
make[1]: *** [all-recursive] Error 1<br>
make[1]: Leaving directory `/tmp/spice-0.6.3'<br>
make: *** [all] Error 2<br>
<br>
<br>
<br>
<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.freedesktop.org/archives/spice-devel/attachments/20110212/f697c6c5/attachment.htm" target="_blank">http://lists.freedesktop.org/archives/spice-devel/attachments/20110212/f697c6c5/attachment.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Fri, 18 Feb 2011 11:13:27 -0500 (EST)<br>
From: Bill Sanford <<a href="mailto:bsanford@redhat.com">bsanford@redhat.com</a>><br>
Subject: [Spice-devel] testing the spice protocol<br>
To: <a href="mailto:spice-devel@lists.freedesktop.org">spice-devel@lists.freedesktop.org</a><br>
Message-ID:<br>
<<a href="mailto:1945593770.253383.1298045607059.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com">1945593770.253383.1298045607059.JavaMail.root@zmail04.collab.prod.int.phx2.redhat.com</a>><br>
<br>
Content-Type: text/plain; charset=utf-8<br>
<br>
Is it possible there is a SPICE line protocol document that explains how the protocol is structured?<br>
<br>
APPENDIX A. Object Definitions - is an example of the description I am looking for to test the SPICE protocol.<br>
<br>
This example is from RFC 2205 (RSVP). There are 14 sections in Appendix A describing how the objects in the protocol are structured. If there isn't one for SPICE, maybe I can get the basic information and make a SPICE line protocol document that we can use.<br>
<br>
Bill<br>
<br>
<br>
APPENDIX A. Object Definitions<br>
<br>
C-Types are defined for the two Internet address families IPv4 and<br>
IPv6. To accommodate other address families, additional C-Types<br>
could easily be defined. These definitions are contained as an<br>
Appendix, to ease updating.<br>
<br>
All unused fields should be sent as zero and ignored on receipt.<br>
<br>
A.1 SESSION Class<br>
<br>
SESSION Class = 1.<br>
<br>
o IPv4/UDP SESSION object: Class = 1, C-Type = 1<br>
<br>
+-------------+-------------+-------------+-------------+<br>
| IPv4 DestAddress (4 bytes) |<br>
+-------------+-------------+-------------+-------------+<br>
| Protocol Id | Flags | DstPort |<br>
+-------------+-------------+-------------+-------------+<br>
<br>
<br>
o IPv6/UDP SESSION object: Class = 1, C-Type = 2<br>
<br>
+-------------+-------------+-------------+-------------+<br>
| |<br>
+ +<br>
| |<br>
+ IPv6 DestAddress (16 bytes) +<br>
| |<br>
+ +<br>
| |<br>
+-------------+-------------+-------------+-------------+<br>
| Protocol Id | Flags | DstPort |<br>
+-------------+-------------+-------------+-------------+<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Sun, 20 Feb 2011 16:20:30 +0200<br>
From: Alon Levy <<a href="mailto:alevy@redhat.com">alevy@redhat.com</a>><br>
Subject: Re: [Spice-devel] [PATCH] protocol: RFC: add common channel<br>
caps for AUTH mechanism selection<br>
To: Marc-Andr? Lureau <<a href="mailto:marcandre.lureau@gmail.com">marcandre.lureau@gmail.com</a>><br>
Cc: Marc-Andr? Lureau <<a href="mailto:mlureau@redhat.com">mlureau@redhat.com</a>>,<br>
<a href="mailto:spice-devel@lists.freedesktop.org">spice-devel@lists.freedesktop.org</a><br>
Message-ID: <<a href="mailto:20110220142029.GC19195@playa.tlv.redhat.com">20110220142029.GC19195@playa.tlv.redhat.com</a>><br>
Content-Type: text/plain; charset=iso-8859-1<br>
<br>
On Sun, Feb 13, 2011 at 04:29:15PM +0100, Marc-Andr? Lureau wrote:<br>
> On Sun, Feb 13, 2011 at 4:30 PM, Hans de Goede <<a href="mailto:hdegoede@redhat.com">hdegoede@redhat.com</a>> wrote:<br>
> > Hi,<br>
> ><br>
> > On 02/13/2011 04:10 PM, Marc-Andr? Lureau wrote:<br>
> >><br>
> >> ----- Original Message -----<br>
> >>><br>
> >>> In general I like, I do have a few remarks though.<br>
> >>><br>
> >>> I would like to state in the spec, and see in this example, that<br>
> >>> SPICE_CHANNEL_CAP_AUTH_SPICE must always be supported, and thus set<br>
> >>> in the capabilities field. This way we ensure that their will always<br>
> >>> be<br>
> >>> one auth method both sides support.<br>
> >>><br>
> >><br>
> >> How would you enforce usage of SASL then? In fact, the way I implemented<br>
> >> it, if you select SASL (from qemu command line), Spice AUTH is then<br>
> >> disabled.<br>
> >><br>
> ><br>
> > Good point, so the example can stay as is. But the spec should contain<br>
> > a blurb that any Spice server / client implementation should support<br>
> > SPICE_CHANNEL_CAP_AUTH_SPICE, and that this can then optionally be disabled<br>
> > through some runtime configuration mechanism. The purpose here being to<br>
> > establish some baseline for interoperability, with say a web browser<br>
> > java applet spice client (remember the discussion about this at fosdem).<br>
> ><br>
> > I agree both sides should be able to deny using this baseline auth<br>
> > mechanism, for administrative reasons. But I would like to make it<br>
> > clear that it should be included in all implementations.<br>
> ><br>
> > Does that make sense?<br>
><br>
> Yes, I'll update the commit comment. Anyway, I will have to update the<br>
> protocol document later (where is it, btw?). So that this comment<br>
> doesn't serve as a reference hopefully.<br>
<br>
It's attached here: <a href="http://spice-space.org/page/Repositories" target="_blank">http://spice-space.org/page/Repositories</a> (look at the bottom)<br>
<br>
><br>
> --<br>
> Marc-Andr? Lureau<br>
> _______________________________________________<br>
> Spice-devel mailing list<br>
> <a href="mailto:Spice-devel@lists.freedesktop.org">Spice-devel@lists.freedesktop.org</a><br>
> <a href="http://lists.freedesktop.org/mailman/listinfo/spice-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/spice-devel</a><br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Sun, 20 Feb 2011 10:50:05 +0100<br>
From: Hans de Goede <<a href="mailto:hdegoede@redhat.com">hdegoede@redhat.com</a>><br>
Subject: Re: [Spice-devel] help for spice-0.6.3<br>
To: <a href="mailto:spice-devel@lists.freedesktop.org">spice-devel@lists.freedesktop.org</a><br>
Message-ID: <<a href="mailto:4D60E3CD.9010704@redhat.com">4D60E3CD.9010704@redhat.com</a>><br>
Content-Type: text/plain; charset=x-gbk; format=flowed<br>
<br>
Hi,<br>
<br>
On 02/12/2011 07:17 AM, ?????? wrote:<br>
> hello??<br>
> I have download the spice-0.6.3.tar.bz2 from <a href="http://www.spice-space.org" target="_blank">http://www.spice-space.org</a> <<a href="http://www.spice-space.org/" target="_blank">http://www.spice-space.org/</a>><br>
> When i compile and install spice, I have encountered some problem, I need some<br>
> help ,Thanks<br>
> The command "configure" have passed , no problem,but in compile process ,there is some mistakes<br>
> The following descibe the situation<br>
> ./configure --includedir=/usr/include --libdir=/usr/lib64 --enable-opengl --enable-gui<br>
<br>
<br>
The problem you are seeing is because you are compiling with --enable-opengl. This cab<br>
be fixed by compiling with this patch:<br>
<a href="http://cgit.freedesktop.org/spice/spice/commit/?id=9f93db6f0732e1e8e9bc8690c1a080d2e6013d68" target="_blank">http://cgit.freedesktop.org/spice/spice/commit/?id=9f93db6f0732e1e8e9bc8690c1a080d2e6013d68</a><br>
<br>
Note though that opengl support is currently not working AFAIK, so it is probably better<br>
to just remove --enable-opengl from your configure arguments.<br>
<br>
Also note that I recently released 0.6.4, which features quite a few bugfixes, so I advice<br>
you to use that version instead.<br>
<br>
Regards,<br>
<br>
Hans<br>
<br>
<br>
> Spice 0.6.3<br>
> ==============<br>
> prefix: /usr/local<br>
> c compiler: gcc<br>
> c++ compiler: g++<br>
> Have XRANDR 1.2: yes<br>
> Support tunneling: no<br>
> Red target: x11<br>
> OpenGL: yes<br>
> GUI: yes<br>
> Now type 'make' to build spice<br>
> make<br>
> red_window.cpp: In member function ??__GLXcontextRec* RedWindow::create_context_gl()??:<br>
> red_window.cpp:2050: error: cannot convert ??__GLXcontextRec*?? to ??__GLXcontextRec**?? in assignment<br>
> red_window.cpp:2053: error: cannot convert ??__GLXcontextRec**?? to ??__GLXcontextRec*?? in return<br>
> make[5]: *** [red_window.o] Error 1<br>
> make[5]: Leaving directory `/tmp/spice-0.6.3/client/x11'<br>
> make[4]: *** [all-recursive] Error 1<br>
> make[4]: Leaving directory `/tmp/spice-0.6.3/client/x11'<br>
> make[3]: *** [all-recursive] Error 1<br>
> make[3]: Leaving directory `/tmp/spice-0.6.3/client'<br>
> make[2]: *** [all] Error 2<br>
> make[2]: Leaving directory `/tmp/spice-0.6.3/client'<br>
> make[1]: *** [all-recursive] Error 1<br>
> make[1]: Leaving directory `/tmp/spice-0.6.3'<br>
> make: *** [all] Error 2<br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Spice-devel mailing list<br>
> <a href="mailto:Spice-devel@lists.freedesktop.org">Spice-devel@lists.freedesktop.org</a><br>
> <a href="http://lists.freedesktop.org/mailman/listinfo/spice-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/spice-devel</a><br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Sun, 20 Feb 2011 17:39:10 +0200<br>
From: Alon Levy <<a href="mailto:alevy@redhat.com">alevy@redhat.com</a>><br>
Subject: Re: [Spice-devel] testing the spice protocol<br>
To: Bill Sanford <<a href="mailto:bsanford@redhat.com">bsanford@redhat.com</a>><br>
Cc: <a href="mailto:spice-devel@lists.freedesktop.org">spice-devel@lists.freedesktop.org</a><br>
Message-ID: <<a href="mailto:20110220153910.GF19195@playa.tlv.redhat.com">20110220153910.GF19195@playa.tlv.redhat.com</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
On Fri, Feb 18, 2011 at 11:13:27AM -0500, Bill Sanford wrote:<br>
> Is it possible there is a SPICE line protocol document that explains how the protocol is structured?<br>
><br>
<br>
1. There is a document about spice 0.4 (0.6 is released and we are approaching 0.8):<br>
<br>
<a href="http://spice-space.org/docs/spice_protocol.pdf" target="_blank">http://spice-space.org/docs/spice_protocol.pdf</a><br>
<br>
2. in the repository the spice.proto file is a pretty succint description, and the enums.h and protocol.h from spice-protocol:<br>
<br>
<a href="http://cgit.freedesktop.org/spice/spice/tree/spice.proto" target="_blank">http://cgit.freedesktop.org/spice/spice/tree/spice.proto</a><br>
this includes all the messages<br>
<br>
<a href="http://cgit.freedesktop.org/spice/spice-protocol/tree/spice/protocol.h" target="_blank">http://cgit.freedesktop.org/spice/spice-protocol/tree/spice/protocol.h</a><br>
this includes the initial handshake (link message) and the wrapper around the messages in spice.proto (SpiceDataHeader)<br>
<br>
<a href="http://cgit.freedesktop.org/spice/spice-protocol/tree/spice/enums.h" target="_blank">http://cgit.freedesktop.org/spice/spice-protocol/tree/spice/enums.h</a><br>
enumerations<br>
<br>
> APPENDIX A. Object Definitions - is an example of the description I am looking for to test the SPICE protocol.<br>
><br>
> This example is from RFC 2205 (RSVP). There are 14 sections in Appendix A describing how the objects in the protocol are structured. If there isn't one for SPICE, maybe I can get the basic information and make a SPICE line protocol document that we can use.<br>
><br>
> Bill<br>
><br>
><br>
> APPENDIX A. Object Definitions<br>
><br>
> C-Types are defined for the two Internet address families IPv4 and<br>
> IPv6. To accommodate other address families, additional C-Types<br>
> could easily be defined. These definitions are contained as an<br>
> Appendix, to ease updating.<br>
><br>
> All unused fields should be sent as zero and ignored on receipt.<br>
><br>
> A.1 SESSION Class<br>
><br>
> SESSION Class = 1.<br>
><br>
> o IPv4/UDP SESSION object: Class = 1, C-Type = 1<br>
><br>
> +-------------+-------------+-------------+-------------+<br>
> | IPv4 DestAddress (4 bytes) |<br>
> +-------------+-------------+-------------+-------------+<br>
> | Protocol Id | Flags | DstPort |<br>
> +-------------+-------------+-------------+-------------+<br>
><br>
><br>
> o IPv6/UDP SESSION object: Class = 1, C-Type = 2<br>
><br>
> +-------------+-------------+-------------+-------------+<br>
> | |<br>
> + +<br>
> | |<br>
> + IPv6 DestAddress (16 bytes) +<br>
> | |<br>
> + +<br>
> | |<br>
> +-------------+-------------+-------------+-------------+<br>
> | Protocol Id | Flags | DstPort |<br>
> +-------------+-------------+-------------+-------------+<br>
> _______________________________________________<br>
> Spice-devel mailing list<br>
> <a href="mailto:Spice-devel@lists.freedesktop.org">Spice-devel@lists.freedesktop.org</a><br>
> <a href="http://lists.freedesktop.org/mailman/listinfo/spice-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/spice-devel</a><br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Spice-devel mailing list<br>
<a href="mailto:Spice-devel@lists.freedesktop.org">Spice-devel@lists.freedesktop.org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/spice-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/spice-devel</a><br>
<br>
<br>
End of Spice-devel Digest, Vol 13, Issue 79<br>
*******************************************<br>
</blockquote></div><br><br clear="all"><br>-- <br><div>Name: анкинд/Ben<br>-----------------------------------------------------------------------------------------------</div>
<div>Mobile: 15800910495<br>Msn: <a href="mailto:liaosongwen@live.cn" target="_blank">liaosongwen@live.cn</a></div>
<div>QQ: 43455134</div><br>