[vbox-dev] Latest build from SVN fails

[Perry Halbert]

I finally got the build to finish by using ./configure --disable-docs
Maybe this will clear itself with future updates.
If I locate the actual offending code of course I will submit it.





On 04/06/2011 10:59 AM, Perry Halbert wrote:
> One last question and I will leave you alone.  I have tried to build 
> to the latest from SVN in Ubuntu 10.10, Debian 6 and Fedora 14 with 
> the exact same failure and in the exact same place.  Has the build 
> restrictions changed since 2011-03-30? This is the last place this has 
> worked for me.
> All complain about undefined symbol: _ZN9RTCString4nposE in 
> release/bin/VBoxManage and then error out.
>
>
>
>
> On 04/06/2011 09:29 AM, Frank Mehnert wrote:
>> Well, doing
>>
>>   svn update -r36479 ; kmk
>>   svn update -r36480 ; kmk
>>
>> would work so you could try to find the relevant revision with a
>> binary search. Unfortunately we cannot reproduce this build
>> failure here.
>>
>> On Wednesday 06 April 2011 16:14:55 Perry Halbert wrote:
>>> I did not intend to mention one specific "r" it is the run of r36479
>>> through r36568.
>>> Since these are released in bulk there is no way for me to specify and
>>> build to a single.
>>> Yes the out directory was deleted. I got burned on that one a long time
>>> ago. I guess I could purge the entire build environment if you think that
>>> is the problem but I have not had to do that before.
>>> Like I said it builds properly through r36478.
>>>
>>> On 04/06/2011 08:57 AM, Frank Mehnert wrote:
>>>> Perry,
>>>>
>>>> r36479 can't be the cause. Did you try to remove the complete output
>>>> directory before rebuilding?
>>>>
>>>> Frank
>>>>
>>>> On Wednesday 06 April 2011 15:49:46 Perry Halbert wrote:
>>>>> Up-to and including r36478 everything builds as it should (just rebuilt
>>>>> yesterday no errors)
>>>>> Build environment is Linux (Ubuntu 10.10) with gcc 4.4.5
>>>>> Building with the latest release r36479 - r36568 causes the failure.
>>>>>
>>>>> Attaching configure.log and I can attach the build.txt if you like.
>>>>>
>>>>> On 04/06/2011 08:34 AM, Frank Mehnert wrote:
>>>>>> Perry,
>>>>>>
>>>>>> which SVN revision is that -- r36568? And is that on Linux, which gcc
>>>>>> version? Our build box is fine ...
>>>>>>
>>>>>> Kind regards,
>>>>>>
>>>>>> Frank
>>>>>>
>>>>>> On Wednesday 06 April 2011 14:44:57 Perry Halbert wrote:
>>>>>>> Just tried compiling the latest from SVN and something is not at all
>>>>>>> happy. mangling?
>>>>>>>
>>>>>>> tstAsmStructs: SUCCESS
>>>>>>> kBuild: Linking VgaBiosBin
>>>>>>> kBuild: Installing VBoxSharedCrOpenGL =>
>>>>>>> /trunk/out/linux.amd64/release/bin/VBoxSharedCrOpenGL.so
>>>>>>> /trunk/out/linux.amd64/release/bin/VBoxManage: symbol lookup error:
>>>>>>> /trunk/out/linux.amd64/release/bin/VBoxManage: undefined symbol:
>>>>>>> _ZN9RTCString4nposE
>>>>>>> kmk: ***
>>>>>>> [/trunk/out/linux.amd64/release/obj/manual/en_US/user_VBoxManage.xml]
>>>>>>> Error 127
>>>>>>> kmk: *** Deleting file
>>>>>>> `/trunk/out/linux.amd64/release/obj/manual/en_US/user_VBoxManage.xml'
>>>>>> _______________________________________________
>>>>>> vbox-dev mailing list
>>>>>> vbox-dev at virtualbox.org
>>>>>> http://vbox.innotek.de/mailman/listinfo/vbox-dev
>>>> _______________________________________________
>>>> vbox-dev mailing list
>>>> vbox-dev at virtualbox.org
>>>> http://vbox.innotek.de/mailman/listinfo/vbox-dev
>
>
> _______________________________________________
> vbox-dev mailing list
> vbox-dev at virtualbox.org
> http://vbox.innotek.de/mailman/listinfo/vbox-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.virtualbox.org/pipermail/vbox-dev/attachments/20110406/af5d30bb/attachment.html>