Re: [Tigervnc-devel] building with glx
On Mon, Nov 15, 2010 at 02:27:22AM +0700, Antoine Martin wrote: Hi, I was running some automated builds with some new compile options (mostly unnecessary - see separate email): ./build-xorg -version 7.4 build --enable-glx --enable-glx-tls --disable-config-hal --disable-config-udev --with-default-font-path=/usr/share/fon ts/X11/misc And it failed to link Xvnc in xorg/xserver/hw/vnc with: /usr/bin/ld: ../../glx/.libs/libglx.a(glxdriswrast.o): undefined reference to symbol 'dlopen@@GLIBC_2.1' /usr/bin/ld: note: 'dlopen@@GLIBC_2.1' is defined in DSO /lib/libdl.so.2 so try adding it to the linker command line /lib/libdl.so.2: could not read symbols: Invalid operation collect2: ld returned 1 exit status I managed to build it by simply adding: -lpthread -ldl Not sure where the correct location for this is... (XSERVER_SYS_LIBS ?) And does using glx actually make any sense? (any difference?) If I remember correctly this is a bug in the old xserver release. On newer operating systems all symbols in binary must be resolved directly during linking, i.e. Xvnc must be linked directly against libdl.so, not against library which is linked against libdl.so. The second approach worked on older OSs and older xserver source depends on this behavior. Newer xserver releases have this bug fixed. And about GLX - if you need Xvnc with GLX extension then you must build it with GLX support :) Regards, Adam -- Adam Tkac, Red Hat, Inc. -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
Re: [Tigervnc-devel] headless git.
On Sun, Nov 14, 2010 at 11:00:18AM +0100, ti...@piments.com wrote: On 11/11/10 12:41, Adam Tkac wrote: On Tue, Nov 09, 2010 at 04:50:12PM +0100, ti...@piments.com wrote: On 11/09/10 16:22, Adam Tkac wrote: On Tue, Nov 09, 2010 at 01:40:28PM +0100, ti...@piments.com wrote: Hi, there seems to be a problem with the instructions in unix/README given to recover xorg tree # git clone git://git.freedesktop.org/git/xorg/xserver xorg Initialized empty Git repository in /root/gcc/xorg/.git/ remote: Counting objects: 114576, done. remote: Compressing objects: 100% (27396/27396), done. remote: Total 114576 (delta 91875), reused 107735 (delta 86267) Receiving objects: 100% (114576/114576), 33.36 MiB | 296 KiB/s, done. Resolving deltas: 100% (91875/91875), done. # cd xorg # git checkout origin/server-1.5-branch Note: checking out 'origin/server-1.5-branch'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b new_branch_name HEAD is now at e1edd9e... security: Grant untrusted windows remove access on all windows. So either my head has become detached ;) or the instructions need updating. git version 1.7.0.4 I can't make out from git --help what this needs to be now. Any hints on an update for the instructions? Hello, does it cause any problem when HEAD is in detached state? You can simply copy (cp -r) all sources and compile Xvnc, can't you? Regards, Adam Thanks Adam, I may be misinterpreting but I would have thought that this meant I was getting current xorg-server HEAD not the 1.7branch that matches the system I'm building on. My aim was to get as close to the running system (kubuntu 10.4) since the doc suggests to get as close as possible to get libvnc to work. Is that not what I need to do or am I mistaken about what HEAD is ? If you need X.Org git repo only for building Xvnc then `git checkoutbranch_name` (where branch_name is origin/server-1.7-branch in you case) is enough. Then simply copy the whole X.Org source to tigervnc/unix/xserver. Regards, Adam Hi, it seems that the new version of git which came with the distro update now spews rather a lot cryptic jargon without stating what HEAD it did get. git pull From . * branchserver-1.7-branch - FETCH_HEAD Already up-to-date. So it seems that HEAD is not the HEAD but each branch has its own HEAD. Most beasts have but one head. It seems git is modelled on the Hydra. Right you are. In git each branch has his own HEAD. Unix tools tend to be silent or terse if successful as it was in previous versions. All this output gave me the impression it was signalling a problem or an unexpected situation. Thanks for you help in clarifying. Ubuntu 10.4 is back to a broken , and now useless, state with tigevnc. It seems like it was more luck than anything that it worked with 9.10. I had to build with -disable-dmx to get around a missing declaration in /hw/mi/miinitext.c and an order reversal made the patch fail. nano ~/gcc/tigervnc/trunk/xorg/xserver/configure.ac.rej AM_INIT_AUTOMAKE([dist-bzip2 foreign]) # order reversed Having sorted that the server did connect but crashed at the first mouse interaction. I'm concluding that tigervnc on kubuntu is a total waste of time unless I can get into serious debugging and probably patching ubuntu xorg. I've had to install x11vnc to get the job done. It's not as fast but it works. I know you're mainly concerned with RedHat development but are you aware of this sort of issue with (k)ubuntu ? At first I thought it was my lack of expertise with getting the build to match but it seems like there are fundamental problems here. I usually don't test Xvnc on Ubuntu. I'm going to check if it is really broken on 10.4 but AFAIK Xvnc works when it is built against X.Org 1.7.X. Regards, Adam -- Adam Tkac, Red Hat, Inc. -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
Re: [Tigervnc-devel] building with glx
On 11/15/2010 08:47 PM, Adam Tkac wrote: On Mon, Nov 15, 2010 at 02:27:22AM +0700, Antoine Martin wrote: Hi, I was running some automated builds with some new compile options (mostly unnecessary - see separate email): ./build-xorg -version 7.4 build --enable-glx --enable-glx-tls --disable-config-hal --disable-config-udev --with-default-font-path=/usr/share/fon ts/X11/misc And it failed to link Xvnc in xorg/xserver/hw/vnc with: /usr/bin/ld: ../../glx/.libs/libglx.a(glxdriswrast.o): undefined reference to symbol 'dlopen@@GLIBC_2.1' /usr/bin/ld: note: 'dlopen@@GLIBC_2.1' is defined in DSO /lib/libdl.so.2 so try adding it to the linker command line /lib/libdl.so.2: could not read symbols: Invalid operation collect2: ld returned 1 exit status I managed to build it by simply adding: -lpthread -ldl Not sure where the correct location for this is... (XSERVER_SYS_LIBS ?) And does using glx actually make any sense? (any difference?) If I remember correctly this is a bug in the old xserver release. On newer operating systems all symbols in binary must be resolved directly during linking, i.e. Xvnc must be linked directly against libdl.so, not against library which is linked against libdl.so. The second approach worked on older OSs and older xserver source depends on this behavior. Newer xserver releases have this bug fixed. So I guess the simple patch I did (prepend the libs to XSERVER_SYS_LIBS) should be merged in some form so that people can continue to build using build-xorg 7.4 on newer systems? As this should not affect/break the build on older systems. And about GLX - if you need Xvnc with GLX extension then you must build it with GLX support :) Hah, yes, obviously. I guess what I am wondering is if this makes any difference to VNC itself, probably not? It just gains the ability to render GL surfaces and VNC doesn't care? Are there any reasons not to include it by default? Cheers Antoine Regards, Adam -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
Re: [Tigervnc-devel] build-xorg 7.5
Whenever I get a chance, I'll try upgrading my version of autoconf and see if that allows me to build successfully with 7.5. On 11/15/10 9:41 AM, Alan Coopersmith wrote: DRC wrote: 'build-xorg -version 7.5' should be considered an experimental feature at the moment. I have never been able to successfully build TigerVNC against Xorg 7.5 on RedHat Enterprise 4 or 5. Currently, I get an error when build-xorg tries to autoconf the Xorg source: configure.ac:468: error: possibly undefined macro: AC_MSG_ERROR If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure:463: error: possibly undefined macro: AM_DEFAULT_VERBOSITY configure:2493: error: possibly undefined macro: AC_PROG_CC_C99 configure:4791: error: possibly undefined macro: AS_VERSION_COMPARE configure:4793: error: possibly undefined macro: AC_MSG_WARN autoreconf: /usr/bin/autoconf failed with exit status: 1 My suspicion is that Xorg 7.5 requires a newer version of autoconf than I have, although its configure.ac file still claims to support 2.57 and later. You may be running into a similar issue. We (X.Org) have fixed that in 7.6 to specify the minimum as autoconf 2.60 in most of the X.Org modules. But I've also not had problems building our (Solaris) TigerVNC packages with our X11R7.5 packages, though we don't use the build-xorg script for that. -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
[Tigervnc-devel] vncviewer Linux - MacOSX locks when X11 focus changes
Hi!
I'm using vncviewer on Linux (X11, ratpoison) to connect to a MacOSX
system.
Almost every time I focus on another window client-side, when I come
back to the vncviewer window, the screen is blocked. The cursor became
the small square, and no action or updating of the screen occurs. I
have to kill vncviewer and restart it every time.
What can be done to avoid that?
--
__Pascal Bourguignon__ http://www.informatimago.com/
A bad day in () is better than a good day in {}.
--
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today
http://p.sf.net/sfu/msIE9-sfdev2dev
___
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
[Tigervnc-devel] [ tigervnc-Feature Request Tracker-2848464 ] Use a VNC Mirror Driver on Win32
Feature Request Tracker item #2848464, was opened at 2009-09-01 14:11 Message generated for change (Comment added) made by jtuc You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1126849aid=2848464group_id=254363 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Windows version Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Kriston Rehberg (kriston) Assigned to: Peter Åstrand (astrand) Summary: Use a VNC Mirror Driver on Win32 Initial Comment: Select a VNC Mirror Driver and integrate it with TigerVNC. There are a few to choose from: RealVNC mirror driver (by RealVNC.com. DFMirage driver from DemoForge LLC (used by TightVNC.com). UltraVNC Mirror Video Driver (used by uvnc.com). -- Comment By: Jochen Tucht (jtuc) Date: 2010-11-16 07:41 Message: I have working code that uses the DFMirage driver. Modifying SDisplayCore::setScreenRect() to return an rdr::U8 * helped me to pass DFMirage's direct access buffer up to the caller so the DeviceFrameBuffer can share it. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=1126849aid=2848464group_id=254363 -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
