Re: [Call For Testing] VirtualBox for FreeBSD! take 6

From: Odhiambo Washington <odhiambo_at_gmail.com>
Date: Mon, 7 Sep 2009 22:18:00 +0300
On Mon, Sep 7, 2009 at 7:45 PM, CmdLnKid <cmdlnkid_at_gmail.com> wrote:

> On Sun, 6 Sep 2009 14:50 -0000, odhiambo wrote:
>
>  On Sun, Sep 6, 2009 at 7:25 PM, Martin Wilke <miwi_at_freebsd.org> wrote:
>>
>>  -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> On Sun, Sep 06, 2009 at 06:11:48PM +0300, Odhiambo Washington wrote:
>>>
>>>> On Sun, Sep 6, 2009 at 1:40 PM, Danny Braniss <danny_at_cs.huji.ac.il>
>>>>
>>> wrote:
>>>
>>>>
>>>>  -----BEGIN PGP SIGNED MESSAGE-----
>>>>>> Hash: SHA1
>>>>>>
>>>>>> Huhu,
>>>>>>
>>>>>> Yes we life and that's good :-).
>>>>>> Changes:
>>>>>>
>>>>>>  - Fix build error when compiling in debug mode on FreeBSD HEAD
>>>>>>  - SemEvent?-r0drv/FreeBSD: Don't use tvtohz for an infinite
>>>>>>
>>>>> timeout.
>>>
>>>>   - Some FreeBSD relate typos
>>>>>>  - Enable shared OpenGL service. Completely untested due to lack of
>>>>>>    appropriate hardware but it compiles at least
>>>>>>  - Add support for shared clipboards. Requires libXt
>>>>>>  - FreeBSD: Implement preemption API for guest SMP and enable
>>>>>>    it (slightly tested). Add neccessary RTMP* methods in userspace
>>>>>>    for the frontends to detect the number of CPUs
>>>>>>  - Runtime/semevent-r0drv-freebsd: Use a sleeping mutex
>>>>>>    instead of a spinlock to fix the problems users are seeing
>>>>>>    (assertions with debugging enabled) while still being able
>>>>>>    to run on 100Hz hosts. No problems detected so far and Solaris
>>>>>>    doesn't use a spin mutex in this code too so it shouldn't do
>>>>>>    any harm (keeping fingers crossed)space for the frontends to
>>>>>>    detect the number of CPUs
>>>>>>  - Add support for curl
>>>>>>  - Add VBoxSharedClipboard
>>>>>>
>>>>>> Ports Changes;
>>>>>>  - Force guestadditions version to 2.2.4
>>>>>>  - Removed Qt3 include replacements (already upstream)
>>>>>>  - Removed cosmetic X11 include path patch
>>>>>>
>>>>>> Please make SURE, your world and kernel is in sync and you've read
>>>>>> the pkg-messages. Also please unload the kernel module before
>>>>>> you update the port ;-).
>>>>>>
>>>>>> Many thx to all Vbox Devs, All supporters, my nice team! :-)
>>>>>>
>>>>>>   http://people.freebsd.org/~miwi/vbox/virtualbox_6.tgz<http://people.freebsd.org/%7Emiwi/vbox/virtualbox_6.tgz>
>>>>>> <http://people.freebsd.org/%7Emiwi/vbox/virtualbox_6.tgz>
>>>>>>
>>>>> <http://people.freebsd.org/%7Emiwi/vbox/virtualbox_6.tgz>
>>>
>>>>
>>>>>>  Happy Testing!
>>>>>>
>>>>>>  ok, so some time has passed, but virtualbox-2.2.51r20457.tar.gz is no
>>>>> longer available, there is a
>>>>>
>>>>>
>>> ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/virtualbox-2.2.51r20457.tar.bz2
>>>
>>>> then again in ports/emulatores/virtualbox the version is 3.0.51r22226,
>>>>>
>>>>> can someone please explain?
>>>>>
>>>>>
>>>>>
>>>>
>>>> And on my FreeBSD 7.2-STABLE, compiling virtualbox fails as follows:
>>>>
>>>>
>>>>
>>>> kBuild: Linking VBoxREM64
>>>> kBuild: Installing VBoxREM64 =>
>>>>
>>>> /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/release/bin/VBox
>>>
>>>> REM64.so
>>>> kmk[2]: Leaving directory
>>>> `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226'
>>>> kmk[1]: Leaving directory
>>>> `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226'
>>>> kBuild: Pass - Programs
>>>> kmk[1]: Entering directory
>>>> `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226'
>>>> kmk[2]: Entering directory
>>>> `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226'
>>>> kBuild: Compiling tstAPI -
>>>>
>>>> /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/src/VBox/Main/testcase/tstAPI.cpp
>>>
>>>> kBuild: Linking tstAPI
>>>> /usr/local/lib/libssl.so.5: undefined reference to `d2i_X509_EXTENSIONS'
>>>> /usr/local/lib/libssl.so.5: undefined reference to
>>>> `ENGINE_get_ssl_client_cert_function'
>>>> /usr/local/lib/libssl.so.5: undefined reference to `HMAC_CTX_set_flags'
>>>> /usr/local/lib/libssl.so.5: undefined reference to `i2d_X509_EXTENSIONS'
>>>> /usr/local/lib/libssl.so.5: undefined reference to
>>>> `ENGINE_load_ssl_client_cert'
>>>> /usr/local/lib/libssl.so.5: undefined reference to `pqueue_size'
>>>> /usr/local/lib/libssl.so.5: undefined reference to `EVP_idea_cbc'
>>>> kmk[2]: ***
>>>>
>>>> [/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/release/obj/tstAPI/tstAPI]
>>>
>>>> Error 1
>>>> The failing command:
>>>> _at_g++               '-Wl,-rpath,/usr/local/lib/virtualbox'   -m32   -o
>>>> /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r
>>>> 22226/out/freebsd.x86/release/obj/tstAPI/tstAPI
>>>>
>>>> /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/
>>>
>>>> release/obj/tstAPI/tstAPI.o   -L/usr/lib  -L/usr/X11R6/lib
>>>> -L/usr/local/lib
>>>> /usr/ports/emulators/virtualbox/work/virtualbo
>>>> x-3.0.51r22226/out/freebsd.x86/release/bin/VBoxRT.so
>>>> /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freeb
>>>> sd.x86/release/lib/VBoxCOM.a
>>>>
>>>> /usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226/out/freebsd.x86/release/bin/VBoxX
>>>
>>>> PCOM.so
>>>> kmk[2]: Leaving directory
>>>> `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226'
>>>> kmk[1]: *** [pass_binaries_this] Error 2
>>>> kmk[1]: Leaving directory
>>>> `/usr/ports/emulators/virtualbox/work/virtualbox-3.0.51r22226'
>>>> kmk: *** [pass_binaries_order] Error 2
>>>> *** Error code 2
>>>>
>>>> Stop in /usr/ports/emulators/virtualbox.
>>>>
>>>>
>>>> I hope someone can advise on what is needed.
>>>>
>>>>
>>> deinstall openssl from ports and try again :)
>>>
>>>
>>>  I remember we had this suggestion before, and either you (or someone
>> else)
>> was going to look into the use of openssl from the ports:-)
>> Looks like I will have to recompile most apps that have linked against
>> openssl, no?
>>
>>
> Just create a backup package of your openssl port with ( pkg_create -b )
> then uninstall the port, rebuild the port in question and ( pkg_add ) the
> openssl port again. This will at least get the port out of the way for you
> to complete the build and will let you determine further action.
>
>
It's not such a critical box. It's a testbed nyway so I did not bother
backing up anything since I will be able to fix any broken packages.
Let me see how it goes. So far so good.... the build process is running...



-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
"If you have nothing good to say about someone, just shut up!."
              -- Lucky Dube
Received on Mon Sep 07 2009 - 17:18:23 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:55 UTC