[prev in list] [next in list] [prev in thread] [next in thread]
List: vbox-dev
Subject: Re: [vbox-dev] svn build fails today.
From: Perry Halbert <phalbert () cox ! net>
Date: 2012-09-13 21:11:19
Message-ID: 50524BF7.5030203 () cox ! net
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Build with VNC Ext Pack enabled completes now. Thank you.
On 09/12/2012 11:58 AM, Frank Mehnert wrote:
> Yes, I think we should add a separate #define for IPv6 which is disabled
> by default and can be enabled manually.
>
> Kind regards,
>
> Frank
>
>
> On Wednesday 12 September 2012 18:35:29 Perry Halbert wrote:
>> Any determination on how to proceed forward with this? The way it
>> stands building the VNC extension pack stops the normal build. From
>> what I see it looks like 0.9.9 is going to be a requirement but that pkg
>> is not native to any stable build I have.
>>
>> On 09/10/2012 07:00 AM, Frank Mehnert wrote:
>>> Hi,
>>>
>>> On Wednesday 05 September 2012 20:55:36 Oliver Loch wrote:
>>>> I installed 12.04 in a VM and checked the headers. It's as Klaus said,
>>>> the rfb.h file defines IPv6 support that is not there.
>>>>
>>>> I got the source from Ubuntu and the main source from sourceforge and
>>>> both are defining LIBVNCSERVER_IPv6 even if it is not there.
>>>>
>>>> Maybe we should check if LIBVNCSERVER_IPv6 is defined and if
>>>> LIBVNCSERVER_PACKAGE_VERSION >= 0.9.9
>>> Yes, such a check is required but such a check is quite difficult
>>> (LIBVNCSERVER_PACKAGE_VERSION is a string). I wonder how a software
>>> is supposed to detect the interface version of that package.
>>>
>>>> Seems to be a bug in libvncserver. Sorry.
>>>>
>>>> @Klaus: what other issues did the patch create?
>>> For instance, the patch uses a Windows function which is Windows 2000+.
>>> Our Guest Additions do also support Windows NT4, therefore we did the
>>> quick hack and disabled the runtime change for Windows hosts.
>>>
>>> There were several other issues and some of them were fixed. See the
>>> current SVN for more details, for example on how to use RTStrCopy().
>>>
>>> Kind regards,
>>>
>>> Frank
>>>
>>>
>>> _______________________________________________
>>> vbox-dev mailing list
>>> vbox-dev@virtualbox.org
>>> https://www.virtualbox.org/mailman/listinfo/vbox-dev
>
>
> _______________________________________________
> vbox-dev mailing list
> vbox-dev@virtualbox.org
> https://www.virtualbox.org/mailman/listinfo/vbox-dev
[Attachment #5 (text/html)]
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font face="Verdana">Build with VNC Ext Pack enabled completes now.
Thank you.<br>
<br>
<br>
<br>
</font>
<div class="moz-cite-prefix">On 09/12/2012 11:58 AM, Frank Mehnert
wrote:<br>
</div>
<blockquote cite="mid:201209121859.01167.frank.mehnert@oracle.com"
type="cite">
<pre wrap="">Yes, I think we should add a separate #define for IPv6 which is \
disabled by default and can be enabled manually.
Kind regards,
Frank
On Wednesday 12 September 2012 18:35:29 Perry Halbert wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Any determination on how to proceed forward with this? The way \
it stands building the VNC extension pack stops the normal build. From
what I see it looks like 0.9.9 is going to be a requirement but that pkg
is not native to any stable build I have.
On 09/10/2012 07:00 AM, Frank Mehnert wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
On Wednesday 05 September 2012 20:55:36 Oliver Loch wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I installed 12.04 in a VM and checked the headers. It's as \
Klaus said, the rfb.h file defines IPv6 support that is not there.
I got the source from Ubuntu and the main source from sourceforge and
both are defining LIBVNCSERVER_IPv6 even if it is not there.
Maybe we should check if LIBVNCSERVER_IPv6 is defined and if
LIBVNCSERVER_PACKAGE_VERSION >= 0.9.9
</pre>
</blockquote>
<pre wrap="">
Yes, such a check is required but such a check is quite difficult
(LIBVNCSERVER_PACKAGE_VERSION is a string). I wonder how a software
is supposed to detect the interface version of that package.
</pre>
<blockquote type="cite">
<pre wrap="">Seems to be a bug in libvncserver. Sorry.
@Klaus: what other issues did the patch create?
</pre>
</blockquote>
<pre wrap="">
For instance, the patch uses a Windows function which is Windows 2000+.
Our Guest Additions do also support Windows NT4, therefore we did the
quick hack and disabled the runtime change for Windows hosts.
There were several other issues and some of them were fixed. See the
current SVN for more details, for example on how to use RTStrCopy().
Kind regards,
Frank
_______________________________________________
vbox-dev mailing list
<a class="moz-txt-link-abbreviated" \
href="mailto:vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</a> <a \
class="moz-txt-link-freetext" \
href="https://www.virtualbox.org/mailman/listinfo/vbox-dev">https://www.virtualbox.org/mailman/listinfo/vbox-dev</a>
</pre>
</blockquote>
</blockquote>
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
vbox-dev mailing list
<a class="moz-txt-link-abbreviated" \
href="mailto:vbox-dev@virtualbox.org">vbox-dev@virtualbox.org</a> <a \
class="moz-txt-link-freetext" \
href="https://www.virtualbox.org/mailman/listinfo/vbox-dev">https://www.virtualbox.org/mailman/listinfo/vbox-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>
_______________________________________________
vbox-dev mailing list
vbox-dev@virtualbox.org
https://www.virtualbox.org/mailman/listinfo/vbox-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic