Re: [Tigervnc-devel] [PATCH] vncserver checks ~/.vnc/passwd when not needed and -TermOnLogout option

2011-03-03 Thread Sebastiaan Breedveld 
This patch needs another line modified, to display the option when run 
with vncserver -h.

The second patch is for the man-page (I have not updated the date of the 
page, I will leave that to you).

Index: unix/vncserver
===
--- unix/vncserver  (revision 4301)
+++ unix/vncserver  (working copy)
@@ -122,7 +122,7 @@
  # Check command line options

  ParseOptions(-geometry,1,-depth,1,-pixelformat,1,-name,1,-kill,1,
- -help,0,-h,0,--help,0,-fp,1,-list,0);
+ -help,0,-h,0,--help,0,-fp,1,-list,0,-fg,0);

  Usage() if ($opt{'-help'} || $opt{'-h'} || $opt{'--help'});

@@ -306,7 +306,15 @@
  }
  $ENV{VNCDESKTOP}= $desktopName;

-system($vncUserDir/xstartup   .quotedString($desktopLog) .  21);
+if ($opt{'-fg'}) {
+system($vncUserDir/xstartup   .quotedString($desktopLog) .  21);
+if (kill 0, `cat $pidFile`) {
+$opt{'-kill'} = ':'.$displayNumber;
+Kill();
+}
+} else {
+system($vncUserDir/xstartup   .quotedString($desktopLog) .  21);
+}

  exit;
@@ -527,6 +535,7 @@
   [-geometrywidthxheight]\n.
   [-pixelformat rgbNNN|bgrNNN]\n.
   [-fpfont-path]\n.
+ [-fg]\n.
  Xvnc-options...\n\n.
 $prog -killX-display\n\n.
 $prog -list\n\n);



Patch for man:

--- vncserver.1.org2011-03-03 11:09:13.209078453 +0100

+++ vncserver.12011-03-03 11:11:15.807863890 +0100

@@ -14,6 +14,7 @@

  .IR format ]

  .RB [ \-fp

  .IR font-path ]

+.RB [ \-fg]

  .RI [ Xvnc-options... ]

  .br

  .BI vncserver \-kill : display#

@@ -105,6 +106,11 @@

  argument allows you to override the above fallback logic and specify a font

  path for Xvnc to use.

  

+.TP

+.B \-fg

+Run vncserver in the foreground. On finishing the Xsession (i.e. user logs

+out from its desktop) the VNC session is also terminated.

+

  .SH FILES

  Several VNC-related files are found in the directory $HOME/.vnc:

  .TP





--
Free Software Download: Index, Search  Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel

Re: [Tigervnc-devel] [PATCH] vncserver checks ~/.vnc/passwd when not needed and -TermOnLogout option

2011-03-03 Thread DRC 
I felt it reasonable enough to check this into trunk.  It tests out fine
for me.  If someone wants to include it in the 1.1 branch, I'm OK with
that as well.


On 3/3/11 4:13 AM, Sebastiaan Breedveld wrote:
 This patch needs another line modified, to display the option when run 
 with vncserver -h.
 
 The second patch is for the man-page (I have not updated the date of the 
 page, I will leave that to you).
 
 Index: unix/vncserver
 ===
 --- unix/vncserver(revision 4301)
 +++ unix/vncserver(working copy)
 @@ -122,7 +122,7 @@
   # Check command line options
 
   ParseOptions(-geometry,1,-depth,1,-pixelformat,1,-name,1,-kill,1,
 -   -help,0,-h,0,--help,0,-fp,1,-list,0);
 +   -help,0,-h,0,--help,0,-fp,1,-list,0,-fg,0);
 
   Usage() if ($opt{'-help'} || $opt{'-h'} || $opt{'--help'});
 
 @@ -306,7 +306,15 @@
   }
   $ENV{VNCDESKTOP}= $desktopName;
 
 -system($vncUserDir/xstartup   .quotedString($desktopLog) .  21);
 +if ($opt{'-fg'}) {
 +system($vncUserDir/xstartup   .quotedString($desktopLog) .  21);
 +if (kill 0, `cat $pidFile`) {
 +$opt{'-kill'} = ':'.$displayNumber;
 +Kill();
 +}
 +} else {
 +system($vncUserDir/xstartup   .quotedString($desktopLog) .  
 21);
 +}
 
   exit;
 @@ -527,6 +535,7 @@
[-geometrywidthxheight]\n.
[-pixelformat rgbNNN|bgrNNN]\n.
[-fpfont-path]\n.
 + [-fg]\n.
   Xvnc-options...\n\n.
  $prog -killX-display\n\n.
  $prog -list\n\n);
 
 
 
 Patch for man:
 
 --- vncserver.1.org2011-03-03 11:09:13.209078453 +0100
 
 +++ vncserver.12011-03-03 11:11:15.807863890 +0100
 
 @@ -14,6 +14,7 @@
 
   .IR format ]
 
   .RB [ \-fp
 
   .IR font-path ]
 
 +.RB [ \-fg]
 
   .RI [ Xvnc-options... ]
 
   .br
 
   .BI vncserver \-kill : display#
 
 @@ -105,6 +106,11 @@
 
   argument allows you to override the above fallback logic and specify a font
 
   path for Xvnc to use.
 
   
 
 +.TP
 
 +.B \-fg
 
 +Run vncserver in the foreground. On finishing the Xsession (i.e. user logs
 
 +out from its desktop) the VNC session is also terminated.
 
 +
 
   .SH FILES
 
   Several VNC-related files are found in the directory $HOME/.vnc:
 
   .TP
 
 
 
 
 
 --
 Free Software Download: Index, Search  Analyze Logs and other IT data in 
 Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
 generated by your applications, servers and devices whether physical, virtual
 or in the cloud. Deliver compliance at lower cost and gain new business 
 insights. http://p.sf.net/sfu/splunk-dev2dev 
 ___
 Tigervnc-devel mailing list
 Tigervnc-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/tigervnc-devel

--
Free Software Download: Index, Search  Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel

Re: [Tigervnc-devel] [PATCH] vncserver checks ~/.vnc/passwd when not needed and -TermOnLogout option

2011-03-03 Thread Adam Tkac 
On Thu, Mar 03, 2011 at 04:54:19AM -0600, DRC wrote:
 I felt it reasonable enough to check this into trunk.  It tests out fine
 for me.  If someone wants to include it in the 1.1 branch, I'm OK with
 that as well.

+1 for inclusion in the 1_1 branch. It seems fine for me, can you pls
merge (or commit) it there, please?

Regards, Adam

 On 3/3/11 4:13 AM, Sebastiaan Breedveld wrote:
  This patch needs another line modified, to display the option when run 
  with vncserver -h.
  
  The second patch is for the man-page (I have not updated the date of the 
  page, I will leave that to you).
  
  Index: unix/vncserver
  ===
  --- unix/vncserver  (revision 4301)
  +++ unix/vncserver  (working copy)
  @@ -122,7 +122,7 @@
# Check command line options
  

  ParseOptions(-geometry,1,-depth,1,-pixelformat,1,-name,1,-kill,1,
  - -help,0,-h,0,--help,0,-fp,1,-list,0);
  + -help,0,-h,0,--help,0,-fp,1,-list,0,-fg,0);
  
Usage() if ($opt{'-help'} || $opt{'-h'} || $opt{'--help'});
  
  @@ -306,7 +306,15 @@
}
$ENV{VNCDESKTOP}= $desktopName;
  
  -system($vncUserDir/xstartup   .quotedString($desktopLog) .  21);
  +if ($opt{'-fg'}) {
  +system($vncUserDir/xstartup   .quotedString($desktopLog) .  
  21);
  +if (kill 0, `cat $pidFile`) {
  +$opt{'-kill'} = ':'.$displayNumber;
  +Kill();
  +}
  +} else {
  +system($vncUserDir/xstartup   .quotedString($desktopLog) .  
  21);
  +}
  
exit;
  @@ -527,6 +535,7 @@
 [-geometrywidthxheight]\n.
 [-pixelformat rgbNNN|bgrNNN]\n.
 [-fpfont-path]\n.
  + [-fg]\n.
Xvnc-options...\n\n.
   $prog -killX-display\n\n.
   $prog -list\n\n);
  
  
  
  Patch for man:
  
  --- vncserver.1.org2011-03-03 11:09:13.209078453 +0100
  
  +++ vncserver.12011-03-03 11:11:15.807863890 +0100
  
  @@ -14,6 +14,7 @@
  
.IR format ]
  
.RB [ \-fp
  
.IR font-path ]
  
  +.RB [ \-fg]
  
.RI [ Xvnc-options... ]
  
.br
  
.BI vncserver \-kill : display#
  
  @@ -105,6 +106,11 @@
  
argument allows you to override the above fallback logic and specify a 
  font
  
path for Xvnc to use.
  

  
  +.TP
  
  +.B \-fg
  
  +Run vncserver in the foreground. On finishing the Xsession (i.e. user logs
  
  +out from its desktop) the VNC session is also terminated.
  
  +
  
.SH FILES
  
Several VNC-related files are found in the directory $HOME/.vnc:
  
.TP
  
  
  
  
  
  --
  Free Software Download: Index, Search  Analyze Logs and other IT data in 
  Real-Time with Splunk. Collect, index and harness all the fast moving IT 
  data 
  generated by your applications, servers and devices whether physical, 
  virtual
  or in the cloud. Deliver compliance at lower cost and gain new business 
  insights. http://p.sf.net/sfu/splunk-dev2dev 
  ___
  Tigervnc-devel mailing list
  Tigervnc-devel@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
 
 --
 Free Software Download: Index, Search  Analyze Logs and other IT data in 
 Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
 generated by your applications, servers and devices whether physical, virtual
 or in the cloud. Deliver compliance at lower cost and gain new business 
 insights. http://p.sf.net/sfu/splunk-dev2dev 
 ___
 Tigervnc-devel mailing list
 Tigervnc-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/tigervnc-devel

-- 
Adam Tkac, Red Hat, Inc.

--
Free Software Download: Index, Search  Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel

Re: [Tigervnc-devel] [PATCH] vncserver checks ~/.vnc/passwd when not needed and -TermOnLogout option

2011-03-03 Thread Adam Tkac 
On Tue, Mar 01, 2011 at 11:25:41AM +0100, Sebastiaan Breedveld wrote:
 Hi all,

Hello,

 2) When using the VeNCrypt security type, the ~/.vnc/passwd is not 
 necessary, yet the user is asked to create one. Same when using the 
 securitytype none. The script now checks for the -SecurityType option 
 and checks wether VeNCrypt type or none is specified. (That is, I am in 
 the assumption that the VeNCrypt type does not use the vnc password.)

You are right, vncserver script shouldn't create passwd file unless
it is needed.

passwd file is needed only when at least one of those types is
specified (case insensitive):

VncAuth or TLSVnc or X509Vnc

By default server allows VncAuth and TLSVnc.

Correct approach is:
1. if -SecurityTypes parameter is not specified, create .vnc/passwd
2. if -SecurityTypes contains at least one of three types specified
   above, create .vnc/passwd
3. otherwise don't create .vnc/passwd

Note in 1. and 2. cases you need to pass -rfbauth parameter, otherwise
Xvnc won't find password file.

With this checks vncserver will create .vnc/passwd only when needed.

Regards, Adam

-- 
Adam Tkac, Red Hat, Inc.

--
Free Software Download: Index, Search  Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel

Re: [Tigervnc-devel] [PATCH] vncserver checks ~/.vnc/passwd when not needed and -TermOnLogout option

2011-03-03 Thread Adam Tkac 
On Thu, Mar 03, 2011 at 01:11:22PM +0100, Sebastiaan Breedveld wrote:
   2) When using the VeNCrypt security type, the ~/.vnc/passwd is not
  necessary, yet the user is asked to create one. Same when using the
  securitytype none. The script now checks for the -SecurityType option
  and checks wether VeNCrypt type or none is specified. (That is, I am in
  the assumption that the VeNCrypt type does not use the vnc password.)
  You are right, vncserver script shouldn't create passwd file unless
  it is needed.
 
  passwd file is needed only when at least one of those types is
  specified (case insensitive):
 
  VncAuth or TLSVnc or X509Vnc
 
  By default server allows VncAuth and TLSVnc.
 
  Correct approach is:
  1. if -SecurityTypes parameter is not specified, create .vnc/passwd
  2. if -SecurityTypes contains at least one of three types specified
  above, create .vnc/passwd
  3. otherwise don't create .vnc/passwd
 
  Note in 1. and 2. cases you need to pass -rfbauth parameter, otherwise
  Xvnc won't find password file.
 
  With this checks vncserver will create .vnc/passwd only when needed.
 
 
 Ok, I was about to get this as well ;) In addition to the above:
 4. do not create .vnc/passwd if -Password, -PasswordFile or -rfbauth is 
 already given.

Right you are, I forgot this case ;)

 Thinking about -Password: is there any sane environment where this is 
 still used?

If I remember correctly someone uses this option for one-time
passwords in his TigerVNC server deployment.

Regards, Adam

-- 
Adam Tkac, Red Hat, Inc.

--
Free Software Download: Index, Search  Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel

Re: [Tigervnc-devel] [Tigervnc-commits] SF.net SVN: tigervnc:[4319] trunk/CMakeLists.txt

2011-03-03 Thread DRC 
Please note that CMake, when used with Visual C++ and NMake, will always
set the default build type to Debug, so it always has to be overridden
on the command line (see BUILDING.txt.)  Setting the default
CMAKE_BUILD_TYPE to Release, per below, is only useful with MinGW or
other types of builds.


On 3/3/11 6:52 AM, ossm...@users.sourceforge.net wrote:
 Revision: 4319
   http://tigervnc.svn.sourceforge.net/tigervnc/?rev=4319view=rev
 Author:   ossman_
 Date: 2011-03-03 12:52:59 + (Thu, 03 Mar 2011)
 
 Log Message:
 ---
 Comment our change of default build type.
 
 Modified Paths:
 --
 trunk/CMakeLists.txt
 
 Modified: trunk/CMakeLists.txt
 ===
 --- trunk/CMakeLists.txt  2011-03-03 12:51:38 UTC (rev 4318)
 +++ trunk/CMakeLists.txt  2011-03-03 12:52:59 UTC (rev 4319)
 @@ -27,6 +27,8 @@
string(REGEX REPLACE \n  BUILD ${BUILD})
  endif()
  
 +# Default to optimised builds instead of debug ones. Our code has no bugs ;)
 +# (CMake makes it fairly easy to toggle this back to Debug if needed)
  if(NOT CMAKE_BUILD_TYPE)
set(CMAKE_BUILD_TYPE Release)
  endif()
 
 
 This was sent by the SourceForge.net collaborative development platform, the 
 world's largest Open Source development site.
 
 --
 Free Software Download: Index, Search  Analyze Logs and other IT data in 
 Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
 generated by your applications, servers and devices whether physical, virtual
 or in the cloud. Deliver compliance at lower cost and gain new business 
 insights. http://p.sf.net/sfu/splunk-dev2dev 
 ___
 Tigervnc-commits mailing list
 tigervnc-comm...@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/tigervnc-commits

--
Free Software Download: Index, Search  Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel

[Tigervnc-devel] [PATCH] specify inetd display range

2011-03-03 Thread Sebastiaan Breedveld 
Hi,

In our environment, we have users that run persistent VNC sessions, and 
on request through inetd. For ease of reminding, I like to give the 
persistent users a low display number (e.g. 1-20). The problem is that a 
new persistent user may have its display blocked by an inetd session.

Therefor I like to specify a display range that inetd can use. The 
following patch allows an optional argument for inetd:
Xvnc -inetd 20-100; % uses displays 20-100
Xvnc -inetd; % uses the default 1-99

Greetings,
Sebastiaan

Ps: while testing incorrect input, I noticed that incorrect input is 
ignored by default. E.g. Xvnc -screen -1 10x20x24 only gives a message 
and the usage options, but runs Xvnc ignoring the incorrect argument.





--- ../../../../unix/xserver/hw/vnc/xvnc.cc2011-02-21 
16:05:15.0 +0100
+++ xvnc.cc2011-03-03 13:58:06.209531786 +0100
@@ -289,7 +289,8 @@
  ErrorF(-geometry WxH  set screen 0's width, height\n);
  ErrorF(-depth D   set screen 0's depth\n);
  ErrorF(-pixelformat fmt   set pixel format (rgbNNN or 
bgrNNN)\n);
-ErrorF(-inetd has been launched from inetd\n);
+ErrorF(-inetd [Start-End] has been launched from inetd\n);
+ErrorF(   Optionally, a display range can be 
given.\n);
  ErrorF(-interface IP_address  listen on specified interface\n);
  ErrorF(-noclipboard   disable clipboard settings 
modification via vncconfig utility\n);
  ErrorF(\nVNC parameters:\n);
@@ -532,26 +533,43 @@

  if (strcmp(argv[i], -inetd) == 0)
  {
+/* Check for optional argument */
+int DisplayStart=1, DisplayEnd=99;
+int argsread = 1;
+
+if ((i+1argc)  (sscanf(argv[i+1],%d-%d,DisplayStart,
+ DisplayEnd) == 2))
+{
+/* Display range argument was specified, check range */
+if (DisplayStart0 || DisplayStartMAXSCREENS || 
DisplayEnd0 || DisplayEnd  MAXSCREENS || DisplayStartDisplayEnd)
+{
+ErrorF(Invalid inetd port range %s\n, 
argv[i+1]);
+UseMsg();
+}
+argsread = 2;
+}
+
  dup2(0,3);
  vncInetdSock = 3;
  close(2);
-
+
  if (!displaySpecified) {
  int port = network::TcpSocket::getSockPort(vncInetdSock);
  int displayNum = port - 5900;
-if (displayNum  0 || displayNum  99 || 
!displayNumFree(displayNum)) {
-for (displayNum = 1; displayNum  100; displayNum++)
+if (displayNum  DisplayStart || displayNum  DisplayEnd || 
!displayNumFree(displayNum)) {
+for (displayNum = DisplayStart; displayNum  DisplayEnd; 
displayNum++)
  if (displayNumFree(displayNum)) break;

-if (displayNum == 100)
+if (displayNum == DisplayEnd+1)
  FatalError(Xvnc error: no free display number for -inetd);
  }

  display = displayNumStr;
  sprintf(displayNumStr, %d, displayNum);
+
  }
-
-return 1;
+return argsread;
  }

  if (strcmp(argv[i], -interface) == 0 ||


--
Free Software Download: Index, Search  Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel

[Tigervnc-devel] [ tigervnc-Bug Tracker-3198439 ] Xvnc -screen -1 10x20x24 crashes

2011-03-03 Thread SourceForge.net 
Bug Tracker item #3198439, was opened at 2011-03-03 14:23
Message generated for change (Tracker Item Submitted) made by atkac
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=1126848aid=3198439group_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: UN*X version
Group: trunk
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Adam Tkac (atkac)
Assigned to: Adam Tkac (atkac)
Summary: Xvnc -screen -1 10x20x24 crashes

Initial Comment:
Xvnc -screen -1 10x20x24 crashes. Needs to be inspected why, probably bad 
options parser.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=1126848aid=3198439group_id=254363

--
Free Software Download: Index, Search  Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel

Re: [Tigervnc-devel] [PATCH] specify inetd display range

2011-03-03 Thread Adam Tkac 
On Thu, Mar 03, 2011 at 02:11:08PM +0100, Sebastiaan Breedveld wrote:
 Hi,

Hello,

 In our environment, we have users that run persistent VNC sessions, and 
 on request through inetd. For ease of reminding, I like to give the 
 persistent users a low display number (e.g. 1-20). The problem is that a 
 new persistent user may have its display blocked by an inetd session.
 
 Therefor I like to specify a display range that inetd can use. The 
 following patch allows an optional argument for inetd:
 Xvnc -inetd 20-100; % uses displays 20-100
 Xvnc -inetd; % uses the default 1-99

This extension of -inetd parameter seems fine for me. This functionality
can be accepted to 1.1 after beta1 release.

Btw would it be possible to also update Xvnc manpage to catch this
extension, please?

 Ps: while testing incorrect input, I noticed that incorrect input is 
 ignored by default. E.g. Xvnc -screen -1 10x20x24 only gives a message 
 and the usage options, but runs Xvnc ignoring the incorrect argument.

Hmm, I get sigsegv when I pass your arguments.

I opened
https://sourceforge.net/tracker/?func=detailaid=3198439group_id=254363atid=1126848
to track this issue because I don't have time for it right now.

Regards, Adam

-- 
Adam Tkac, Red Hat, Inc.

--
Free Software Download: Index, Search  Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel

Re: [Tigervnc-devel] Ready for 1.1 beta

2011-03-03 Thread Adam Tkac 
On Tue, Feb 22, 2011 at 12:17:32PM -0500, Antoine Martin wrote:
 On 02/21/2011 10:46 AM, DRC wrote:
  I've spun a new build from r4305:
 
  http://www.virtualgl.org/DeveloperInfo/TigerVNCPreReleases
 
  It checks out on all known issues I had, so from my point of view, we're
  ready for beta.  I propose that this build and source tarball become the
  official release.
 I've just let the build bot loose on this version and some of the debian 
 distros failed to build the server (but the viewer built ok):
 * intrepid, karmic, lucid, maverick, squeeze went ok
 * hardy, natty and lenny failed...
 
 Sorry, I don't have much more to report than this:
 /usr/src/tigervnc-1.0.90-r4305/configure: line 4089: syntax error near 
 unexpected token `build_libtool_libs,'
 /usr/src/tigervnc-1.0.90-r4305/configure: line 4089: `
 _LT_DECL(build_libtool_libs, enable_shared, 0,'
 
 I will look into it when I get a chance.
 IIRC, r4288 was building ok, but r4305 does not.
 (r4241 certainly did build ok since I have debs archived for that version)

Just for information, how did you build Xvnc? Via unix/build-xorg
script? Or directly in unix/xserver/ via autoreconf  configure 
make?

Regards, Adam

-- 
Adam Tkac, Red Hat, Inc.

--
Free Software Download: Index, Search  Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel

Re: [Tigervnc-devel] Ready for 1.1 beta

2011-03-03 Thread DRC 
On 3/3/11 9:08 AM, Antoine Martin wrote:
 Does 7.5 work now? Shall I be using that instead? (I wasn't because
 there were some strange build errors previously - maybe fixed now)

7.5 doesn't work on RHEL 4 or 5, but it may work on more recent systems
with newer autotools.

--
Free Software Download: Index, Search  Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Tigervnc-devel mailing list
Tigervnc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tigervnc-devel