[vbox-dev] SVN r-51319

Wed May 28 12:48:09 GMT 2014

Michael,

"VBOX_NO_DOCS_TRANSLATIONS := 1" does the trick.

I read the changes to the DOCs and for the life of me could not find 
this until you added it in r-51431. I could have sworn that I saw it 
once before I posted the issue, but couldn't. I do know this issue 
happened when you started pulling from the build server (as far as a 
time line).

Thanks,

Perry

On 05/28/2014 07:11 AM, Michael Thayer wrote:
> Perry,
>
> Please try current SVN with "VBOX_NO_DOCS_TRANSLATIONS := 1".
>
> Regards,
>
> Michael
>
> On 28/05/14 08:23, Michael Thayer wrote:
>> Hello Perry,
>>
>> Strange, I can't reproduce your error with the exact revision and your
>> LocalConfig.kmk.  Tell me if you have any other ideas, like local
>> changes ("svn status" in the build root directory will tell you)... and
>> you said that you removed the "out" directory before building.
>>
>> Regards,
>>
>> Michael
>>
>> On 27/05/14 17:44, Perry Halbert wrote:
>>> Hi Michael,
>>>
>>> Sorry for the confusion, Misha was the first to reply and after all 
>>> I am
>>> the worlds worst with names :-(.
>> No problem, it was mainly just to save you confusion!
>>
>> -Michael
>>
>>> OSE r51319 does not have this issue with the DOCs the new update OSE
>>> r51407 I was instructed to try is where it goes south.
>>>
>>> Normally my configure line is blank ( ./configure )
>>>
>>> Of course the values change depending on what I want to do at the given
>>> time, but for the most part these are what I use in my LocalConfig.kmk.
>>>
>>> ------------------
>>> VBOX_VERSION_MAJOR = 4
>>> VBOX_VERSION_MINOR = 3
>>> VBOX_VERSION_BUILD = 51
>>> VBOX_VERSION_STRING_RAW =
>>> $(VBOX_VERSION_MAJOR).$(VBOX_VERSION_MINOR).$(VBOX_VERSION_BUILD)
>>> VBOX_VERSION_STRING = $(VBOX_VERSION_STRING_RAW)$(VBOX_BUILD_PUBLISHER)
>>> VBOX_PACKAGE_STRING =
>>> $(VBOX_PACKAGE_OS)_$(VBOX_PACKAGE_ARCH)_$(VBOX_PACKAGE_DIST)
>>> VBOX_PACKAGE_DIST = LINUX-MINT
>>> VBOX_VENDOR := PerryG
>>> VBOX_VENDOR_SHORT :=PgVMs
>>> VBOX_PRODUCT := PerryG Virtual Machines
>>> VBOX_WITH_WARNINGS_AS_ERRORS :=
>>> VBOX_WITH_DOCS_TRANSLATIONS :=
>>> VBOX_WITH_DOCS_SDKREF := 1
>>> VBOX_WITH_WEBSERVICES :=
>>> VBOX_WITH_WEBSERVICES_SSL :=
>>> VBOX_WITH_TESTCASES :=
>>> VBOX_WITH_TESTSUITE :=
>>> VBOX_WITH_UDPTUNNEL := 1
>>> VBOX_WITH_VDE := 1
>>> VBOX_WITH_EXTPACK_VNC := 1
>>> VBOX_GSOAP_INSTALLED :=
>>>
>>> ----------------------
>>>
>>> Disabling the build of the DOCs ( ./configure --disable-docs ) allowed
>>> the build (OSE r51407) to complete.
>>>
>>> Perry
>>>
>>>
>>>
>>>
>>> On 05/27/2014 10:06 AM, Michael Thayer wrote:
>>>> Hello Perry,
>>>>
>>>> I was unable to reproduce this with a fresh OSE r51319 check-out with
>>>> "VOX_WITH_DOCS_TRANSLATIONS :=" in LocalConfig.kmk.  Would you be able
>>>> to provide the full contents of LocalConfig.kmk and your configure
>>>> command line (see env.sh)?
>>>>
>>>> By the way, just for clarity, I am not Misha (at least not the same
>>>> Misha!), and I am the person who is responsible for the Guest
>>>> Additions no longer remembering the resolution from one boot to the
>>>> next (and who wrote to you about it previously).
>>>>
>>>> Regards,
>>>>
>>>> Michael
>>>>
>>>> On 26/05/14 22:20, Perry Halbert wrote:
>>>>> That would work *if* you don't delete the out folder before 
>>>>> compiling to
>>>>> keep from having issues.
>>>>> Have things changed to where you don't need to remove the out folder?
>>>>>
>>>>> Perry
>>>>>
>>>>> On 05/26/2014 03:15 PM, mikhail sennikovsky wrote:
>>>>>> Seems like OSE build is broken. As a tmp workaround, I'd suggest you
>>>>>> to do "touch 
>>>>>> /trunk/out/linux.amd64/release/bin/UserManual_fr_FR.pdf"
>>>>>> to create a dummy UserManual_fr_FR.pdf
>>>>>>
>>>>>> Mikhail
>>>>>>
>>>>>> On 26.05.2014 23:50, Perry Halbert wrote:
>>>>>>> Very weird.  Broken make?
>>>>>>>
>>>>>>> kBuild: Installing symlink
>>>>>>> /trunk/out/linux.amd64/release/bin/UserManual.pdf
>>>>>>> kmk: *** No rule to make target
>>>>>>> `/trunk/out/linux.amd64/release/bin/UserManual_fr_FR.pdf', 
>>>>>>> needed by
>>>>>>> `/trunk/out/linux.amd64/release/obj/Installer/linux/archive/UserManual_fr_FR.pdf'. 
>>>>>>>
>>>>>>>
>>>>>>> Stop.
>>>>>>> kmk: *** Waiting for unfinished jobs....
>>>>>>> kmk: *** Exiting with status 2
>>>>>>>
>>>>>>>
>>>>>>> I have VBOX_WITH_DOCS_TRANSLATIONS :=  in my LocalConfig.kmk to 
>>>>>>> *not
>>>>>>> build the French translation.
>>>>>>>
>>>>>>>
>>>>>>> On 05/26/2014 02:31 PM, mikhail sennikovsky wrote:
>>>>>>>> Perry,
>>>>>>>>
>>>>>>>> Please give a try to the latest OSE. The issue should be solved
>>>>>>>> there.
>>>>>>>>
>>>>>>>> Thanks for reporting it!
>>>>>>>> Mikhail
>>>>>>>>
>>>>>>>> On 26.05.2014 17:15, Perry Halbert wrote:
>>>>>>>>> Good day Misha,
>>>>>>>>>
>>>>>>>>> Linux and Windows both.
>>>>>>>>>
>>>>>>>>> Mint -16 or 17 both 64-bit.
>>>>>>>>> Windows-7 also 64-bit
>>>>>>>>>
>>>>>>>>> Host = Ubuntu 12.04 Base 64-bit
>>>>>>>>>
>>>>>>>>> I have also noticed that if you start the Linux guest ( stop and
>>>>>>>>> start not saved state ) it does not remember the screen size and
>>>>>>>>> starts in 1024x768.
>>>>>>>>>
>>>>>>>>> Resize the screen to a larger size and the screen goes black 
>>>>>>>>> (VBox
>>>>>>>>> Main manager preview windows is showing proper content though 
>>>>>>>>> ) and
>>>>>>>>> then if you pause the guest the video is rendered with the darker
>>>>>>>>> screen and then un-pausing the video is rendered properly.
>>>>>>>>>
>>>>>>>>> I am also attaching a log for this.  I started the guest and
>>>>>>>>> resized the screen and it went black (time = 1:54).
>>>>>>>>> I waited for about 6 minutes and then paused/unpaused (time = 
>>>>>>>>> 7:42)
>>>>>>>>> everything fine.
>>>>>>>>>
>>>>>>>>> Have a great day,
>>>>>>>>> Perry
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 05/26/2014 05:29 AM, mikhail sennikovsky wrote:
>>>>>>>>>> Hi Perry,
>>>>>>>>>>
>>>>>>>>>> which guest are you saving/restoring?
>>>>>>>>>> Could you post me the logs for guest save and restore sessions?
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Misha
>>>>>>>>>>
>>>>>>>>>> On 23.05.2014 20:58, Perry Halbert wrote:
>>>>>>>>>>> FYI Saved state does not work in r51319.  It saves just fine 
>>>>>>>>>>> but
>>>>>>>>>>> re-starting aborts. Stated reason is failure to load HGCM.
>>>>>>>>>>>
>>>>>>>>>>> 00:00:16.877831 AssertLogRel
>>>>>>>>>>> /trunk/src/VBox/Main/src-client/HGCM.cpp(1306) static int
>>>>>>>>>>> HGCMService::LoadState(PSSMHANDLE): <NULL>
>>>>>>>>>>>
>>>>>>>>>>> 00:00:16.877851 rc=VERR_SSM_UNEXPECTED_DATA VBoxSharedCrOpenGL
>>>>>>>>>>>
>>>>>>>>>>> 00:00:16.877917 SSM: LoadExec failed for 'HGCM' instance #0
>>>>>>>>>>> (version 2, pass 0xffffffff): VERR_SSM_UNEXPECTED_DATA
>>>>>>>>>>>
>>>>>>>>>>> 00:00:16.877979 VMSetError:
>>>>>>>>>>> /trunk/src/VBox/VMM/VMMR3/SSM.cpp(8495) int 
>>>>>>>>>>> ssmR3LoadExecV2(PVM,
>>>>>>>>>>> PSSMHANDLE); rc=VERR_SSM_UNEXPECTED_DATA
>>>>>>>>>>>
>>>>>>>>>>> 00:00:16.877984 VMSetError: Failed to load unit 'HGCM'
>>>>>>>>>>>
>>>>>>>>>>> 00:00:16.897583 Changing the VM state from 'LOADING' to
>>>>>>>>>>> 'LOAD_FAILURE'.
>>>>>>>>>>>
>>>>>>>>>>> 00:00:16.897676 Changing the VM state from 'LOAD_FAILURE' to
>>>>>>>>>>> 'POWERING_OFF'.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Let me know if you need the full log.
>>>>>>>>>>>
>>>>>>>>>>> Perry
>>>>
>>>
>>
>>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.virtualbox.org/pipermail/vbox-dev/attachments/20140528/9296888c/attachment.html>