Virtualbox does not lunch (FREEBSD 7.2 STABLE)

[Jeronimo Calvo]

 /usr/local/lib/virtualbox
-bash: /usr/local/lib/virtualbox: is a directory
[iscariote@ ~]$ /usr/local/lib/virtualbox/VirtualBox
-bash: /usr/local/lib/virtualbox/VirtualBox: No such file or directory

No in any of them...

2009/9/24 Craig Butler <craig001 at lerwick.hopto.org>:
> Hi,
>
> Do you have any thing in /usr/local/lib/virtualbox/ ??
>
> $ ls -l /usr/local/bin/VirtualBox
> lrwxr-xr-x  1 root  wheel  36 Sep 21 08:28 /usr/local/bin/VirtualBox ->
> /usr/local/lib/virtualbox/VirtualBox
>
> Cheers
>
> /Craig B
>
> On Thu, 2009-09-24 at 18:35 +0000, Jeronimo Calvo wrote:
>
> Hi all!
>
> Im still having following issue with VirtualBox: (not able to launch
> it when installed from source with option: VBOX_WITH_HARDENING = 0)
>
> log:
>
> # cd /usr/ports/emulators/virtualbox/
> # ls
> Makefile        files           pkg-message     work
> distinfo        pkg-descr       pkg-plist
> # make install
> # exit
> exit
> $ VirtualBox
> bash: VirtualBox: command not found
> $ whereis VirtualBox
> VirtualBox:
> $ pkg_info | grep virtualbox
> virtualbox-3.0.51.r22226 A general-purpose full virtualizer for x86 hardware
>
>
>
> It seems to be installed, but not soft-linked properly, any ideas?
>
>
> 2009/9/18 Lowell Gilbert <freebsd-questions-local at be-well.ilk.org>:
>> Don't top-post, please.
>>
>> Jeronimo Calvo <jeronimocalvop at googlemail.com> writes:
>>
>>> for some reason, it gives me the same error... the funny thing is
>>> pkgdb gives me a nice colection of errors as well :D
>>>
>>>
>>> # pkg_info | grep virtualbox
>>> virtualbox-3.0.51.r22226 A general-purpose full virtualizer for x86
>>> hardware
>>>
>>> # pkg_delete -f virtualbox-3.0.51.r22226
>>>
>>> pkg_delete: unable to completely remove directory
>>> '/usr/local/lib/virtualbox'
>>> pkg_delete: couldn't entirely delete package (perhaps the packing list is
>>> incorrectly specified?)
>>
>> This error isn't serious.  You can look in that directory, see what's
>> left, and either submit a fix for the port to remove it, or perhaps find
>> out that there is local configuration that the port *shouldn't* be
>> removing.
>>
>> --
>> Lowell Gilbert, embedded/networking software engineer, Boston area
>>                http://be-well.ilk.org/~lowell/
>>
>