virtualbox-ose port fails (12.1)

Christoph Kukulies kuku at kukulies.org
Fri May 15 08:40:59 UTC 2020


I knew why I initially began compiling the virtual box. Then I got the advice here to use the pckg. Trying that I ended up in a failing (panicking) vboxvfs.ko module.

The got another advice to stick with compiling the port since it better matches the distributed kernel (12.1.)

Anyway, now I’m stuck in builing the virtualbox-ose port.

First there was a glitch when pythin 2.7 had to be built. a security warning had to be overwritten by

DISABLE_VUNERABILITIES=yes

That done the next time the build stops at

===>   virtualbox-ose-5.2.32_1 depends on file: /usr/local/bin/python2.7 - found
===>   virtualbox-ose-5.2.32_1 depends on file: /usr/local/bin/sdl-config - found
===>   virtualbox-ose-5.2.32_1 depends on file: /usr/local/bin/clang60 - not found
===>   llvm60-6.0.1_7 depends on executable: sphinx-build - not found
===>   py36-sphinx-1.6.5_2,1 depends on package: py36-Jinja2>=2.3 - not found
===>   py36-Jinja2-2.10.1 depends on package: py36-setuptools>0 - not found
===>  Installing for py36-setuptools-41.2.0
===>  Checking if py36-setuptools is already installed
===>   Registering installation for py36-setuptools-41.2.0 as automatic
Installing py36-setuptools-41.2.0...
pkg-static: py36-setuptools-41.2.0 conflicts with py37-setuptools-44.0.0 (installs files into the same place).  Problematic file: /usr/local/bin/easy_install
*** Error code 70

Stop.
make[7]: stopped in /usr/ports/devel/py-setuptools
*** Error code 1

Stop.
make[6]: stopped in /usr/ports/devel/py-Jinja2
*** Error code 1

Stop.
make[5]: stopped in /usr/ports/devel/py-Jinja2
*** Error code 1

Stop.
make[4]: stopped in /usr/ports/textproc/py-sphinx
*** Error code 1

Stop.
make[3]: stopped in /usr/ports/devel/llvm60
*** Error code 1

Stop.
make[2]: stopped in /usr/ports/devel/llvm60
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/emulators/virtualbox-ose
*** Error code 1

Stop.
make: stopped in /usr/ports/emulators/virtualbox-ose
# 

I’m wondering anyway why two python versions (2 and 3) have to be built . But that left aside, how do I now get around this obstacle?


—
Christoph





More information about the freebsd-questions mailing list