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