spice-space-devel Mailing List for Spice Space
Brought to you by:
ykamay
Menu
▾
▴
spice-space-devel
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(133) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
(75) |
Feb
(12) |
Mar
(2) |
Apr
(4) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|
From: <pan...@zt...> - 2010-10-15 03:25:55
|
1. how does qemu virtualize vertex shader,pixel shader,TMU(texture mapping unit) ? I can't find the relate source codes. 2. The frame buffer resides in the host or guest os ? -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender. This message has been scanned for viruses and Spam by ZTE Anti-Spam system. |
|
From: Frédéric G. <fre...@ya...> - 2010-05-23 10:58:08
|
Are your spice client/spice server/guest drivers all 0.4, or all from latest unstable branch? Don't try to mix them, I can definetly confirm that it will not work... Frederic. hi, i downloaded binaries for qxl driver from http://www.spice-space.org/download.html and tried to install qxl driver on windows xp 32 bit machine. iam getting error. The status is "This device cannot start. (Code 10)". can u please tell why iam unable ti install this .. thanks and regards sridhar ------------------------------------------------------------------------------ _______________________________________________ Spice-space-devel mailing list Spi...@li... https://lists.sourceforge.net/lists/listinfo/spice-space-devel |
|
From: Arnon G. <ag...@re...> - 2010-05-23 09:21:38
|
Seems like a version mismatch between the driver and the qemu qxl device. I will check the versions & update you. Arnon sridhar wrote: > hi, > i downloaded binaries for qxl driver from > http://www.spice-space.org/download.html and tried to install qxl driver on > windows xp 32 bit machine. iam getting error. The status is "This device > cannot start. (Code 10)". > can u please tell why iam unable ti install this .. > > thanks and regards > sridhar > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > > > ------------------------------------------------------------------------ > > _______________________________________________ > Spice-space-devel mailing list > Spi...@li... > https://lists.sourceforge.net/lists/listinfo/spice-space-devel > |
|
From: sridhar <sri...@gm...> - 2010-04-30 07:19:22
|
hi, i downloaded binaries for qxl driver from http://www.spice-space.org/download.html and tried to install qxl driver on windows xp 32 bit machine. iam getting error. The status is "This device cannot start. (Code 10)". can u please tell why iam unable ti install this .. thanks and regards sridhar |
|
From: AFAHOUNKO D. <afa...@gm...> - 2010-04-26 08:41:02
|
works great ! thks ! :) hehehe... On 04/26/2010 07:44 AM, Uri Lublin wrote: > On 04/26/2010 09:50 AM, AFAHOUNKO Danny wrote: >> Hi folks, >> i've installed spice on F12 64bit and it works like a charm. >> i tried to build the spice client on F12 x86 bit but it still failed !! >> >> -----latest error-------- >> [...] >> make[3]: Leaving directory `/root/spice/client/x11/images' >> make[2]: Leaving directory `/root/spice/client/x11/images' >> make[2]: Entering directory `/root/spice/client/x11' >> g++ -DHAVE_CONFIG_H -I. -I../.. -DCAIRO_CANVAS_ACCESS_TEST >> -DCAIRO_CANVAS_CACHE -DCAIRO_CANVAS_CACH_IS_SHARED >> -DCAIRO_CANVAS_NO_CHUNKS -DUSE_GLZ -DUSE_OGL -I. -I.. -I../../common >> -I../../common/linux -I../../client -I/usr/include/alsa >> -I/usr/include/ffmpeg-spice -I/usr/include/cairo-spice >> -I/usr/include/pixman-spice-1 -I/usr/include/freetype2 >> -I/usr/include/libpng12 -Wall -Wno-sign-compare -Werror >> -Wno-deprecated-declarations -g -O3 -MT red_peer.o -MD -MP -MF >> .deps/red_peer.Tpo -c -o red_peer.o `test -f '../../client/red_peer.cpp' >> || echo './'`../../client/red_peer.cpp >> ../../client/red_peer.cpp: In member function ‘void >> RedPeer::connect_secure(const RedPeer::ConnectionOptions&, uint32_t)’: >> ../../client/red_peer.cpp:177: error: invalid conversion from ‘const >> SSL_METHOD*’ to ‘SSL_METHOD*’ >> make[2]: *** [red_peer.o] Error 1 >> make[2]: Leaving directory `/root/spice/client/x11' >> make[1]: *** [install-recursive] Error 1 >> make[1]: Leaving directory `/root/spice/client/x11' >> make: *** [install-recursive] Error 1 >> >> ------------------------- >> >> >> There is a way to build 32bit client rpm from source ? >> or even if i could have a procedure to compile it. > > The problem is probably different versions of the openssl library. > Try the attached patch. Does it help ? > > > HTH, > Uri. > -- AFAHOUNKO Danny Administrateur Réseaux & Système d'Information - CICA-RE Red Hat Certified Engineer - RHCE Gsm: +228 914.55.89 / +228 953.54.50 Tel: +228 223.62.62 |
|
From: Uri L. <ur...@re...> - 2010-04-26 07:44:47
|
On 04/26/2010 09:50 AM, AFAHOUNKO Danny wrote:
> Hi folks,
> i've installed spice on F12 64bit and it works like a charm.
> i tried to build the spice client on F12 x86 bit but it still failed !!
>
> -----latest error--------
> [...]
> make[3]: Leaving directory `/root/spice/client/x11/images'
> make[2]: Leaving directory `/root/spice/client/x11/images'
> make[2]: Entering directory `/root/spice/client/x11'
> g++ -DHAVE_CONFIG_H -I. -I../.. -DCAIRO_CANVAS_ACCESS_TEST
> -DCAIRO_CANVAS_CACHE -DCAIRO_CANVAS_CACH_IS_SHARED
> -DCAIRO_CANVAS_NO_CHUNKS -DUSE_GLZ -DUSE_OGL -I. -I.. -I../../common
> -I../../common/linux -I../../client -I/usr/include/alsa
> -I/usr/include/ffmpeg-spice -I/usr/include/cairo-spice
> -I/usr/include/pixman-spice-1 -I/usr/include/freetype2
> -I/usr/include/libpng12 -Wall -Wno-sign-compare -Werror
> -Wno-deprecated-declarations -g -O3 -MT red_peer.o -MD -MP -MF
> .deps/red_peer.Tpo -c -o red_peer.o `test -f '../../client/red_peer.cpp'
> || echo './'`../../client/red_peer.cpp
> ../../client/red_peer.cpp: In member function ‘void
> RedPeer::connect_secure(const RedPeer::ConnectionOptions&, uint32_t)’:
> ../../client/red_peer.cpp:177: error: invalid conversion from ‘const
> SSL_METHOD*’ to ‘SSL_METHOD*’
> make[2]: *** [red_peer.o] Error 1
> make[2]: Leaving directory `/root/spice/client/x11'
> make[1]: *** [install-recursive] Error 1
> make[1]: Leaving directory `/root/spice/client/x11'
> make: *** [install-recursive] Error 1
>
> -------------------------
>
>
> There is a way to build 32bit client rpm from source ?
> or even if i could have a procedure to compile it.
The problem is probably different versions of the openssl library.
Try the attached patch. Does it help ?
HTH,
Uri.
|
|
From: AFAHOUNKO D. <afa...@gm...> - 2010-04-26 06:57:35
|
Hi folks, i've installed spice on F12 64bit and it works like a charm. i tried to build the spice client on F12 x86 bit but it still failed !! -----latest error-------- [...] make[3]: Leaving directory `/root/spice/client/x11/images' make[2]: Leaving directory `/root/spice/client/x11/images' make[2]: Entering directory `/root/spice/client/x11' g++ -DHAVE_CONFIG_H -I. -I../.. -DCAIRO_CANVAS_ACCESS_TEST -DCAIRO_CANVAS_CACHE -DCAIRO_CANVAS_CACH_IS_SHARED -DCAIRO_CANVAS_NO_CHUNKS -DUSE_GLZ -DUSE_OGL -I. -I.. -I../../common -I../../common/linux -I../../client -I/usr/include/alsa -I/usr/include/ffmpeg-spice -I/usr/include/cairo-spice -I/usr/include/pixman-spice-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -Wall -Wno-sign-compare -Werror -Wno-deprecated-declarations -g -O3 -MT red_peer.o -MD -MP -MF .deps/red_peer.Tpo -c -o red_peer.o `test -f '../../client/red_peer.cpp' || echo './'`../../client/red_peer.cpp ../../client/red_peer.cpp: In member function ‘void RedPeer::connect_secure(const RedPeer::ConnectionOptions&, uint32_t)’: ../../client/red_peer.cpp:177: error: invalid conversion from ‘const SSL_METHOD*’ to ‘SSL_METHOD*’ make[2]: *** [red_peer.o] Error 1 make[2]: Leaving directory `/root/spice/client/x11' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/root/spice/client/x11' make: *** [install-recursive] Error 1 ------------------------- There is a way to build 32bit client rpm from source ? or even if i could have a procedure to compile it. thx! -- AFAHOUNKO Danny Administrateur Réseaux & Système d'Information - CICA-RE Red Hat Certified Engineer - RHCE Gsm: +228 914.55.89 / +228 953.54.50 Tel: +228 223.62.62 |
|
From: Yaniv K. <yk...@re...> - 2010-03-01 14:14:28
|
On 3/1/2010 3:43 PM, fok wrote:
> Hi Guys,
> I'm testing spice on my network and I've two workstations on which the
> spice-client either immediately crashes, or after about half an hour.
> The one on which spice immediately crashes is a dell optiplex 280gx,
> windows XP SP3 with an Intel 915 graphics chip. The machine just shuts
> down with a blue screen and c000021a error. It reboots then.
> The other machine is a windows 7 Acer laptop with ATI Radeon 4200 card
> built in. It works for about half an hour and then also crashes.
> Since these both crash with a blue screen there's nothing in the
> eventviewer.
> I have a workstation with an Intel 845 (older machine) on which the
> client is stable, I can work on that one for days without trouble.
> Is there any development on the windows binairies, will there be updates?
> Regards, Jan Fokkelman
Jan, if it's not too much trouble, could you perform some analysis on
the BSOD?
Here are simple instructions on how to do it:
1. Make sure that the memory was dumped. To configure it (in XP, in W2K
it's similar):
1.
Start -> Control Panel -> System -> Advanced -> 'Startup and
Recovery - click on the 'Settings' button
2. Make sure under 'System failure' 'Automatically restart' is NOT
checked; 'Write debugging information' should be set to 'Complete
memory dump'. You may need to restart the OS.
2. After a BSOD occurred, wait until it is completely written before
rebooting the OS.
3. After the OS completed booting, you can look at the memory dump
(usually, under %SystemRoot%\memory.dmp - which is usually
c:\windows\memory.dmp), using the Debugging Tools for Windows (install
from http://www.microsoft.com/whdc/devtools/debugging/installx86.Mspx ).
Note! If you use it on 64bit OS, you need the amd64 version).
4. Open WindDbg (Start->All Programs->Debugging Tools for Windows
->WinDbg), go to File->Symbol File Path and enter:
SRV*http://msdl.microsoft.com/download/symbols
If you have your own symbols as well, use:
srv*c:\symbols*http://msdn.microsoft.com/download/symbols
5. Open the crash dump using File->Open Crash Dump
6. Run the command '!analyze -v' (this may take a while).
Copy the whole output - it may be relevant.
TIA,
Y.
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
>
>
> _______________________________________________
> Spice-space-devel mailing list
> Spi...@li...
> https://lists.sourceforge.net/lists/listinfo/spice-space-devel
>
|
|
From: fok <j.f...@sc...> - 2010-03-01 14:07:13
|
Hi Guys, I'm testing spice on my network and I've two workstations on which the spice-client either immediately crashes, or after about half an hour. The one on which spice immediately crashes is a dell optiplex 280gx, windows XP SP3 with an Intel 915 graphics chip. The machine just shuts down with a blue screen and c000021a error. It reboots then. The other machine is a windows 7 Acer laptop with ATI Radeon 4200 card built in. It works for about half an hour and then also crashes. Since these both crash with a blue screen there's nothing in the eventviewer. I have a workstation with an Intel 845 (older machine) on which the client is stable, I can work on that one for days without trouble. Is there any development on the windows binairies, will there be updates? Regards, Jan Fokkelman |
|
From: Yaniv K. <yk...@re...> - 2010-02-18 19:20:50
|
----- "Jan Fokkelman" <j.f...@sc...> wrote: > Hi Guys, > > I have a windowsdomain (I work for an elementary school) and want to > go virtual. I've been testing spice and i'm very very impressed with > it. I have a dualcore with 3G ram and I can serve 5 > XP-virtual-workstations at the same time using spice, all playing > flashgames and/or watching a movie. Sound and video synchronous. Great > stuff, never seen before, not with citrix speedscreen either. > I have some questions I hope you can find the time to answer: > -When will there be a management-system for administration a la > virt-manager? The only solution I'm aware of is RHEV for desktops. > -Will there be an 'on demand' webinterface-like thing on the thin > clients? (And when is the 32bit linux-spice-client available?) > -Is there a way of making flash/swf be processed on the thin client > instead of on the server, in the same way that it works for avi,mpg? Spice handle all video formats in the same way. The differences that you see are probably result of the way players render the video. > > Regards and keep it up! > > Jan > ------------------------------------------------------------------------------ > SOLARIS 10 is the OS for Data Centers - provides features such as > DTrace, > Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW > http://p.sf.net/sfu/solaris-dev2dev > _______________________________________________ > Spice-space-devel mailing list > Spi...@li... > https://lists.sourceforge.net/lists/listinfo/spice-space-devel |
|
From: Arnon G. <ag...@re...> - 2010-02-16 07:19:22
|
Ravi, As I said, you should install the qxl & vdiport drivers and verify they are active before starting the service. Windows 7 compatible agent/service & 64 bit drivers will soon be available from the website. Ravi Kumar Vemulapalli wrote: > Arnon, I installed it on windows XP but 32 bit machine, i thought > windows libraries took care of it. Can these be downloadable from > spice site for windows separately? also does this woek for windows 7 > too? -R > > --- On *Mon, 2/15/10, Arnon Gilboa /<ag...@re...>/* wrote: > > > From: Arnon Gilboa <ag...@re...> > Subject: Re: [Spice-space-devel] windows XP sp3 - spice installation > To: "Ravi Kumar Vemulapalli" <rve...@ya...> > Cc: spi...@li... > Date: Monday, February 15, 2010, 7:15 AM > > Hello Ravi, > First of all, you should install the qxl & vdiport drivers and > verify they are active. > Now, how did you install the agent and service? > Regards, > Arnon > > Ravi Kumar Vemulapalli wrote: > > I have issues starting vdservice/vdagent in windows XP sp3, does > SPICE install on it? Here is what i see, > > The RHEV Spice Agent service is starting. > > The RHEV Spice Agent service could not be started. > > The service did not report an error. > > More help is available by typing NET HELPMSG 3534. > > I couldn't find you any sipcec.log, and also let me know if > there is any documentation on it? thanks > > Ravi > > > > > ------------------------------------------------------------------------ > > > > > ------------------------------------------------------------------------------ > > SOLARIS 10 is the OS for Data Centers - provides features such > as DTrace, > > Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW > > http://p.sf.net/sfu/solaris-dev2dev > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Spice-space-devel mailing list > > Spi...@li... > </mc/compose?to=Spi...@li...> > > https://lists.sourceforge.net/lists/listinfo/spice-space-devel > > > > |
|
From: Arnon G. <ag...@re...> - 2010-02-15 07:15:40
|
Hello Ravi, First of all, you should install the qxl & vdiport drivers and verify they are active. Now, how did you install the agent and service? Regards, Arnon Ravi Kumar Vemulapalli wrote: > I have issues starting vdservice/vdagent in windows XP sp3, does SPICE > install on it? Here is what i see, > > The RHEV Spice Agent service is starting. > The RHEV Spice Agent service could not be started. > The service did not report an error. > More help is available by typing NET HELPMSG 3534. > > I couldn't find you any sipcec.log, and also let me know if there is > any documentation on it? > > thanks > Ravi > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, > Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW > http://p.sf.net/sfu/solaris-dev2dev > ------------------------------------------------------------------------ > > _______________________________________________ > Spice-space-devel mailing list > Spi...@li... > https://lists.sourceforge.net/lists/listinfo/spice-space-devel > |
|
From: Ravi K. V. <rve...@ya...> - 2010-02-14 21:45:43
|
I have issues starting vdservice/vdagent in windows XP sp3, does SPICE install on it? Here is what i see,
The RHEV Spice Agent service is starting.
The RHEV Spice Agent service could not be started.
The service did not report an error.
More help is available by typing NET HELPMSG 3534.
I couldn't find you any sipcec.log, and also let me know if there is any documentation on it?
thanks
Ravi
|
|
From: Jan F. <j.f...@sc...> - 2010-02-12 12:01:52
|
Hi Guys, I have a windowsdomain (I work for an elementary school) and want to go virtual. I've been testing spice and i'm very very impressed with it. I have a dualcore with 3G ram and I can serve 5 XP-virtual-workstations at the same time using spice, all playing flashgames and/or watching a movie. Sound and video synchronous. Great stuff, never seen before, not with citrix speedscreen either. I have some questions I hope you can find the time to answer: -When will there be a management-system for administration a la virt-manager? -Will there be an 'on demand' webinterface-like thing on the thin clients? (And when is the 32bit linux-spice-client available?) -Is there a way of making flash/swf be processed on the thin client instead of on the server, in the same way that it works for avi,mpg? Regards and keep it up! Jan |
|
From: Alexander L. <al...@re...> - 2010-02-11 14:43:24
|
We're moving all the spice-space.org infrastructure (mailing lists, bug tracker and git) to freedesktop.org. The new lists are availible at: http://lists.freedesktop.org/mailman/listinfo/spice-announce http://lists.freedesktop.org/mailman/listinfo/spice-commits http://lists.freedesktop.org/mailman/listinfo/spice-devel All current subscribers have been moved over to the new lists. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Alexander Larsson Red Hat, Inc al...@re... ale...@gm... He's a suicidal zombie paranormal investigator gone bad. She's a manipulative communist traffic cop fleeing from a Satanic cult. They fight crime! |
|
From: Yaniv K. <yk...@re...> - 2010-02-01 13:28:26
|
On 01/22/2010 01:44 PM, Frédéric Grelot wrote: > I was just browsing vdesktop/qemu/hw/qxl.c code and found what I think may be a typo : > there is a function like this one, called at the end of qxl_init(...) : > static void regitser_interface(PCIQXLDevice *d) > Maybe you should replace it with "register_interface"... > Is now fixed in the master branch, thanks. > And, by the way, nobody had any idea about my segfault in qxl F13 driver?... > > Frédéric. > > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for Conference > attendees to learn about information security's most important issues through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > _______________________________________________ > Spice-space-devel mailing list > Spi...@li... > https://lists.sourceforge.net/lists/listinfo/spice-space-devel > |
|
From: Yaniv K. <yk...@re...> - 2010-02-01 13:26:49
|
Applied, thanks. On 01/12/2010 01:27 PM, Uri Lublin wrote: > This only affects spice-client and spice-server builds that are > configured with --with-spice-common (that are using > an installed spice-common package). > > Version has been increased to 0.4.2 lately. > > Signed-off-by: Uri Lublin<ur...@re...> > --- > configure.ac.shared | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/configure.ac.shared b/configure.ac.shared > index 8c686c1..eca9943 100644 > --- a/configure.ac.shared > +++ b/configure.ac.shared > @@ -177,7 +177,7 @@ AC_ARG_WITH(spice-common, > [use_spice_common=no]) > > if test "x$use_spice_common" != "xno"; then > - PKG_CHECK_MODULES(SPICE_COMMON, spice-common = 0.4.1) > + PKG_CHECK_MODULES(SPICE_COMMON, spice-common = 0.4.2) > SPICE_COMMON_SRCDIR=$(pkg-config --variable=common_src_dir spice-common) > fi > > |
|
From: Yaniv K. <yk...@re...> - 2010-02-01 13:15:17
|
Applied, thanks. On 01/13/2010 06:17 PM, Uri Lublin wrote: > Also adding some information to toplevel (spice) README > And do not touch README when running autogen.sh > > Signed-off-by: Uri Lublin<ur...@re...> > --- > README | 5 ++++- > autogen.sh.shared | 2 +- > client/README | 12 ++++++++++++ > common/README | 12 ++++++++++++ > server/README | 12 ++++++++++++ > 5 files changed, 41 insertions(+), 2 deletions(-) > create mode 100644 client/README > create mode 100644 common/README > create mode 100644 server/README > |
|
From: Dave A. <ai...@gm...> - 2010-01-27 21:59:52
|
On Thu, Jan 28, 2010 at 4:49 AM, Jan Fokkelman <j.f...@sc...> wrote: > Hi, > I've got spice working locally but how do I connect from a remote windows > workstation? > Locally, if I start the guest I can do: > spicec -h 127.0.0.1 -p 5930 and it works. > On a remote windows workstation I do > spicec -h ip_of_guest -p 5930, spicec tries to connect for some time and > dies. I also tried > spicec -h ip_of_host -p 5930 > and nothing. > How do I connect? Both guest and host are connected and pingable within my > LAN. Firewall rules let the port in? Dave. |
|
From: Jan F. <j.f...@sc...> - 2010-01-27 19:07:11
|
Hi, I've got spice working locally but how do I connect from a remote windows workstation? Locally, if I start the guest I can do: spicec -h 127.0.0.1 -p 5930 and it works. On a remote windows workstation I do spicec -h ip_of_guest -p 5930, spicec tries to connect for some time and dies. I also tried spicec -h ip_of_host -p 5930 and nothing. How do I connect? Both guest and host are connected and pingable within my LAN. Regards, Jan |
|
From: Frédéric G. <fre...@ya...> - 2010-01-22 11:45:25
|
I was just browsing vdesktop/qemu/hw/qxl.c code and found what I think may be a typo : there is a function like this one, called at the end of qxl_init(...) : static void regitser_interface(PCIQXLDevice *d) Maybe you should replace it with "register_interface"... And, by the way, nobody had any idea about my segfault in qxl F13 driver?... Frédéric. |
|
From: Darren X. <dj...@gm...> - 2010-01-22 11:12:21
|
thanks for your help, it works, and on ubuntu the corresponding lib is libglu1-mesa-dev, just type *apt-get install libglu1-mesa-dev* to install it. :) --djxiong 2010/1/21 Yonit Halperin <yha...@re...> > Hi, > > Please try to install mesa-libGLU-devel. > > > > Thanks for using Spice, > > Yonit. > > > ------------------------------ > > *From:* Darren Xiong [mailto:dj...@gm...] > *Sent:* Thursday, January 21, 2010 11:14 AM > *To:* spi...@li... > *Subject:* [Spice-space-devel] error occurred when configure spice > onubuntu9.04 > > > > I tried to install spice on my ubuntu 9.04 desktop, I followed the spice > user manual <http://www.spice-space.org/docs/spice_user_manual.pdf> step > by step, but when I went to the 2.4.1 of the manual, I encountered an error > when I configured the source. I guess that I have some libraries > missed(maybe about opengl),but I don't know exactly what and which version > missed. > Any hint or help is appreciated. > Below is the outputs when run autogen. > thanks. > > root@keqisoft-desktop:/opt/spice# tar -xjvf spice_0_4.tar.bz2 > ...... > ...... > *(many out puts but I make sure that the tar procedure is successful)* > then > root@keqisoft-desktop:/opt/spice/spice# ./autogen.sh > -includedir=/usr/include --libdir=/usr/lib64 > > using autoconf for autoconf > > > checking for automake >= 1.7... > > testing automake... > found 1.10.2 > > using libtoolize for libtool > > > Setting up spice toplevel > > ./autogen.sh: running `libtoolize --copy --force' > libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'. > libtoolize: copying file `./ltmain.sh' > libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'. > libtoolize: copying file `m4/libtool.m4' > libtoolize: copying file `m4/ltoptions.m4' > libtoolize: copying file `m4/ltsugar.m4' > libtoolize: copying file `m4/ltversion.m4' > libtoolize: copying file `m4/lt~obsolete.m4' > libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. > ./autogen.sh: running `aclocal' > ./autogen.sh: running `autoheader' > ./autogen.sh: running `automake --add-missing --gnu' > ./autogen.sh: running `autoconf' > ./autogen.sh: running `./configure --enable-maintainer-mode > -includedir=/usr/include --libdir=/usr/lib64' > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /bin/mkdir -p > checking for gawk... no > checking for mawk... mawk > checking whether make sets $(MAKE)... yes > checking whether to enable maintainer-specific portions of Makefiles... yes > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ISO C89... none needed > checking for style of include used by make... GNU > checking dependency style of gcc... gcc3 > checking for g++... g++ > checking whether we are using the GNU C++ compiler... yes > checking whether g++ accepts -g... yes > checking dependency style of g++... gcc3 > checking for a BSD-compatible install... /usr/bin/install -c > checking build system type... x86_64-unknown-linux-gnu > checking host system type... x86_64-unknown-linux-gnu > checking for a sed that does not truncate output... /bin/sed > checking for grep that handles long lines and -e... /bin/grep > checking for egrep... /bin/grep -E > checking for fgrep... /bin/grep -F > checking for ld used by gcc... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B > checking the name lister (/usr/bin/nm -B) interface... BSD nm > checking whether ln -s works... yes > checking the maximum length of command line arguments... 1572864 > checking whether the shell understands some XSI constructs... yes > checking whether the shell understands "+="... yes > checking for /usr/bin/ld option to reload object files... -r > checking for objdump... objdump > checking how to recognize dependent libraries... pass_all > checking for ar... ar > checking for strip... strip > checking for ranlib... ranlib > checking command to parse /usr/bin/nm -B output from gcc object... ok > checking how to run the C preprocessor... gcc -E > checking for ANSI C header files... yes > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking for dlfcn.h... yes > checking whether we are using the GNU C++ compiler... (cached) yes > checking whether g++ accepts -g... (cached) yes > checking dependency style of g++... (cached) gcc3 > checking how to run the C++ preprocessor... g++ -E > checking for objdir... .libs > checking if gcc supports -fno-rtti -fno-exceptions... no > checking for gcc option to produce PIC... -fPIC -DPIC > checking if gcc PIC flag -fPIC -DPIC works... yes > checking if gcc static flag -static works... yes > checking if gcc supports -c -o file.o... yes > checking if gcc supports -c -o file.o... (cached) yes > checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared > libraries... yes > checking whether -lc should be explicitly linked in... no > checking dynamic linker characteristics... GNU/Linux ld.so > checking how to hardcode library paths into programs... immediate > checking whether stripping libraries is possible... yes > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... yes > checking whether to build static libraries... yes > checking for ld used by g++... /usr/bin/ld -m elf_x86_64 > checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes > checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared > libraries... yes > checking for g++ option to produce PIC... -fPIC -DPIC > checking if g++ PIC flag -fPIC -DPIC works... yes > checking if g++ static flag -static works... yes > checking if g++ supports -c -o file.o... yes > checking if g++ supports -c -o file.o... (cached) yes > checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared > libraries... yes > checking dynamic linker characteristics... GNU/Linux ld.so > checking how to hardcode library paths into programs... immediate > checking whether gcc and cc understand -c and -o together... yes > checking for x86 or x86-64 platform... 64 bit > checking for native Win32... no > checking for some Win32 platform... no > checking for cos in -lm... yes > checking for clock_gettime in -lrt... yes > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for LOG4CPP... yes > checking for QCAIRO... yes > checking for CELT051... yes > checking for FFMPEG... yes > checking avcodec.h usability... no > checking avcodec.h presence... no > checking for avcodec.h... no > checking for ALSA... yes > checking for SSL... yes > checking for glBlendFunc in -lGL... no > checking for gluSphere in -lGLU... no > configure: error: GL libraries not available > root@keqisoft-desktop:/opt/spice/spice# > > > -- djxiong > -- KeQiSoft Co.,LTD Mobile: +86 158 2122 8272 Tel: +86 21 5415 4833 Fax: +86 21 6460 6232 Website: www.keqisoft.com |
|
From: Yonit H. <yha...@re...> - 2010-01-21 11:36:52
|
Hi, Please try to install mesa-libGLU-devel. Thanks for using Spice, Yonit. _____ From: Darren Xiong [mailto:dj...@gm...] Sent: Thursday, January 21, 2010 11:14 AM To: spi...@li... Subject: [Spice-space-devel] error occurred when configure spice onubuntu9.04 I tried to install spice on my ubuntu 9.04 desktop, I followed the spice user manual <http://www.spice-space.org/docs/spice_user_manual.pdf> step by step, but when I went to the 2.4.1 of the manual, I encountered an error when I configured the source. I guess that I have some libraries missed(maybe about opengl),but I don't know exactly what and which version missed. Any hint or help is appreciated. Below is the outputs when run autogen. thanks. root@keqisoft-desktop:/opt/spice# tar -xjvf spice_0_4.tar.bz2 ...... ...... (many out puts but I make sure that the tar procedure is successful) then root@keqisoft-desktop:/opt/spice/spice# ./autogen.sh -includedir=/usr/include --libdir=/usr/lib64 using autoconf for autoconf checking for automake >= 1.7... testing automake... found 1.10.2 using libtoolize for libtool Setting up spice toplevel ./autogen.sh: running `libtoolize --copy --force' libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'. libtoolize: copying file `./ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'. libtoolize: copying file `m4/libtool.m4' libtoolize: copying file `m4/ltoptions.m4' libtoolize: copying file `m4/ltsugar.m4' libtoolize: copying file `m4/ltversion.m4' libtoolize: copying file `m4/lt~obsolete.m4' libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. ./autogen.sh: running `aclocal' ./autogen.sh: running `autoheader' ./autogen.sh: running `automake --add-missing --gnu' ./autogen.sh: running `autoconf' ./autogen.sh: running `./configure --enable-maintainer-mode -includedir=/usr/include --libdir=/usr/lib64' checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... yes checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking for a BSD-compatible install... /usr/bin/install -c checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1572864 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for ar... ar checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking whether we are using the GNU C++ compiler... (cached) yes checking whether g++ accepts -g... (cached) yes checking dependency style of g++... (cached) gcc3 checking how to run the C++ preprocessor... g++ -E checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for ld used by g++... /usr/bin/ld -m elf_x86_64 checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC -DPIC checking if g++ PIC flag -fPIC -DPIC works... yes checking if g++ static flag -static works... yes checking if g++ supports -c -o file.o... yes checking if g++ supports -c -o file.o... (cached) yes checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether gcc and cc understand -c and -o together... yes checking for x86 or x86-64 platform... 64 bit checking for native Win32... no checking for some Win32 platform... no checking for cos in -lm... yes checking for clock_gettime in -lrt... yes checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for LOG4CPP... yes checking for QCAIRO... yes checking for CELT051... yes checking for FFMPEG... yes checking avcodec.h usability... no checking avcodec.h presence... no checking for avcodec.h... no checking for ALSA... yes checking for SSL... yes checking for glBlendFunc in -lGL... no checking for gluSphere in -lGLU... no configure: error: GL libraries not available root@keqisoft-desktop:/opt/spice/spice# -- djxiong |
|
From: Darren X. <dj...@gm...> - 2010-01-21 09:13:43
|
I tried to install spice on my ubuntu 9.04 desktop, I followed the spice user manual <http://www.spice-space.org/docs/spice_user_manual.pdf> step by step, but when I went to the 2.4.1 of the manual, I encountered an error when I configured the source. I guess that I have some libraries missed(maybe about opengl),but I don't know exactly what and which version missed. Any hint or help is appreciated. Below is the outputs when run autogen. thanks. root@keqisoft-desktop:/opt/spice# tar -xjvf spice_0_4.tar.bz2 ...... ...... *(many out puts but I make sure that the tar procedure is successful)* then root@keqisoft-desktop:/opt/spice/spice# ./autogen.sh -includedir=/usr/include --libdir=/usr/lib64 using autoconf for autoconf checking for automake >= 1.7... testing automake... found 1.10.2 using libtoolize for libtool Setting up spice toplevel ./autogen.sh: running `libtoolize --copy --force' libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'. libtoolize: copying file `./ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'. libtoolize: copying file `m4/libtool.m4' libtoolize: copying file `m4/ltoptions.m4' libtoolize: copying file `m4/ltsugar.m4' libtoolize: copying file `m4/ltversion.m4' libtoolize: copying file `m4/lt~obsolete.m4' libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. ./autogen.sh: running `aclocal' ./autogen.sh: running `autoheader' ./autogen.sh: running `automake --add-missing --gnu' ./autogen.sh: running `autoconf' ./autogen.sh: running `./configure --enable-maintainer-mode -includedir=/usr/include --libdir=/usr/lib64' checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... yes checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking for a BSD-compatible install... /usr/bin/install -c checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for fgrep... /bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1572864 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for ar... ar checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking whether we are using the GNU C++ compiler... (cached) yes checking whether g++ accepts -g... (cached) yes checking dependency style of g++... (cached) gcc3 checking how to run the C++ preprocessor... g++ -E checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for ld used by g++... /usr/bin/ld -m elf_x86_64 checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC -DPIC checking if g++ PIC flag -fPIC -DPIC works... yes checking if g++ static flag -static works... yes checking if g++ supports -c -o file.o... yes checking if g++ supports -c -o file.o... (cached) yes checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether gcc and cc understand -c and -o together... yes checking for x86 or x86-64 platform... 64 bit checking for native Win32... no checking for some Win32 platform... no checking for cos in -lm... yes checking for clock_gettime in -lrt... yes checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for LOG4CPP... yes checking for QCAIRO... yes checking for CELT051... yes checking for FFMPEG... yes checking avcodec.h usability... no checking avcodec.h presence... no checking for avcodec.h... no checking for ALSA... yes checking for SSL... yes checking for glBlendFunc in -lGL... no checking for gluSphere in -lGLU... no configure: error: GL libraries not available root@keqisoft-desktop:/opt/spice/spice# -- djxiong |
|
From: Frédéric G. <fre...@ya...> - 2010-01-16 19:51:53
|
> I don't know when I was wrong : qxl was built from git, so should I > update spice to the latest git version? > (remember me? I already had the same problem, actually then opposite > one with winXP : version mismatch between spice and qxl). > I will try it anyway as soon as I have time for it, but if you have > any other Idea...! Well, I re-built spice server and "vdesktop" from git, but with no success... So I still need your help! Frederic. |
8 messages has been excluded from this view by a project administrator.
