virtualbox-ose port fails (12.1)
Christoph Kukulies
kuku at kukulies.org
Sat May 16 09:37:21 UTC 2020
Just want to let you know that virtualbox-ose now finished compiling and it’s working.
Now I’m trying to find where vboxvfs.ko is hidden. Doesn’t seem to be in virtualbox-ose-kmod.
Possibly in -additions which I’m compiling right now.
—
Christoph
> Am 16.05.2020 um 00:11 schrieb Mario Lobo <lobo at bsd.com.br>:
>
> On Fri, May 15, 2020 at 4:39 PM Christoph Kukulies <kuku at kukulies.org <mailto:kuku at kukulies.org>>
> wrote:
>
>> I did the following:
>>
>> ln -s /usr/local/bin/phython3.7 /usr/local/bin/python
>>
>> (not sure whether this was healthy at all)
>>
>> Then went into
>>
>> /usr/ports/x11/libinput
>>
>> make install
>>
>> (this went through without a hitch)
>>
>> Then continued with building virtualbox-ose
>>
>> and it got over the point where it wanted to build libinput since the
>> request got satisfied.
>>
>> Don’t know what time to build the rest I would have to expect at all.
>>
>> I also have a desktop with WIndows 10 that has 16GB and an AMD Hex core
>> (whatnot GHz). Maybe I should dedicate this one to FreeBSD :) ?)
>>
>> —
>> Christoph
>>
>>
>>> Am 15.05.2020 um 21:17 schrieb Trond Endrestøl <
>> trond.endrestol at ximalas.info>:
>>>
>>> On Fri, 15 May 2020 21:02+0200, Christoph Kukulies wrote:
>>>
>>>>> Am 15.05.2020 um 20:39 schrieb Trond Endrestøl <
>> trond.endrestol at ximalas.info>:
>>>>>
>>>>> On Fri, 15 May 2020 20:18+0200, Christoph Kukulies wrote:
>>>>>
>>>>>>> Am 15.05.2020 um 19:15 schrieb Mario Lobo <lobo at bsd.com.br>:
>>>>>>>
>>>>>>> On Fri, May 15, 2020 at 8:57 AM Christoph Kukulies <
>> kuku at kukulies.org <mailto:kuku at kukulies.org>>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Am 15.05.2020 um 11:18 schrieb Trond Endrestøl <
>>>>>>>> trond.endrestol at ximalas.info <mailto:trond.endrestol at ximalas.info
>>>> :
>>>>>>>>>
>>>>>>>>> On Fri, 15 May 2020 10:40+0200, Christoph Kukulies wrote:
>>>>>>>>>
>>>>>>>>>> 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.
>>>>>>>>>>
>>>>>>>>
>>>>>>> [snip...]
>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 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?
>>>>>>>>>
>>>>>>>>> According to ports/Mk/bsd.default-versions.mk, Python 3.7 is both
>> the
>>>>>>>>> default Python version and the default Python3 version.
>>>>>>>>>
>>>>>>>>> Have you locked the Pythons to 3.6 in /etc/make.conf or in an
>>>>>>>>> equivalent file such as /usr/local/etc/poudriere.d/make.conf?
>>>>>>>>
>>>>>>>> Thanks. Yes, I had some of these tools installed as pkg and already
>>>>>>>> deleted them and the correct tools got built out of the ports tree.
>>>>>>>>
>>>>>>>>> Do you mix prebuilt packages and packages built yourself?
>>>>>>>>>
>>>>>>>>> You should recompile devel/py-setuptools at py36 so that it abstains
>> from
>>>>>>>>> creating the /usr/local/bin/easy_install symlink.
>>>>>>>>
>>>>>>>> Done so, thanks.
>>>>>>>>
>>>>>>> Doesn't Vbox require python 2.7 to be built?
>>>>>>>
>>>>>>> I get a warning about python 2.7 everytime I build VBox.
>>>>>>>
>>>>>>> I have this in make.conf:
>>>>>>>
>>>>>>> DEFAULT_VERSIONS=perl5=5.30 linux=c7_64 ssl=base python=3.7
>> python2=2.7
>>>>>>> python3=3.7
>>>>>>>
>>>>>>> --
>>>>>>> Mario Lobo
>>>>>>
>>>>>> In this vein my vbox make stops at the next obstacle:
>>>>>> ===> qt5-gui-5.13.0_1 depends on shared library: libharfbuzz.so -
>> found (/usr/local/lib/libharfbuzz.so)
>>>>>> ===> qt5-gui-5.13.0_1 depends on shared library: libinput.so - not
>> found
>>>>>> ===> libinput-1.12.6_1 needs Python 3.4 at least, but 2.7 was
>> specified.
>>>>>> *** Error code 1
>>>>>>
>>>>>> Stop.
>>>>>> make[5]: stopped in /usr/ports/x11/libinput
>>>>>> *** Error code 1
>>>>>>
>>>>>> Stop.
>>>>>> make[4]: stopped in /usr/ports/x11-toolkits/qt5-gui
>>>>>> *** Error code 1
>>>>>>
>>>>>> Stop.
>>>>>> make[3]: stopped in /usr/ports/x11-toolkits/qt5-declarative
>>>>>> *** Error code 1
>>>>>>
>>>>>> Stop.
>>>>>> make[2]: stopped in /usr/ports/devel/qt5-linguisttools
>>>>>> *** 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
>>>>>> #
>>>>>
>>>>> lang/python controls what the /usr/local/bin/python symlink points to.
>>>>> It might still be pointing to Python 2.7 when it should be pointing to
>>>>> Python 3.7.
>>>>>
>>>>> You have two options:
>>>>>
>>>>> 1. Recreate and reinstall lang/python.
>>>>> 2. Change the /usr/local/bin/python symlink yourself.
>>>>
>>>>
>>>> Thanks. But I don’t have /usr/local/bin/python:
>>>
>>> I see. Maybe you could try "ln -s python3.7 /usr/local/bin/python"
>>> just to see if it helps. If not, then I'm out of suggestions.
>>>
>>>> lrwxr-xr-x 1 root wheel 11 May 15 11:40 pybabel -> pybabel-3.6
>>>> -rwxr-xr-x 1 root wheel 384 May 15 11:40 pybabel-3.6
>>>> -rwxr-xr-x 1 root wheel 84 May 15 10:04 pydoc2.7
>>>> -rwxr-xr-x 1 root wheel 84 May 15 10:22 pydoc3.6
>>>> -rwxr-xr-x 1 root wheel 84 Apr 23 03:20 pydoc3.7
>>>> lrwxr-xr-x 1 root wheel 14 May 15 11:44 pygmentize ->
>> pygmentize-3.6
>>>> -rwxr-xr-x 1 root wheel 399 May 15 11:44 pygmentize-3.6
>>>> -r-xr-xr-x 1 root wheel 15192 May 15 10:03 python2.7
>>>> -r-xr-xr-x 1 root wheel 1769 May 15 10:04 python2.7-config
>>>> -r-xr-xr-x 2 root wheel 15392 May 15 10:21 python3.6
>>>> lrwxr-xr-x 1 root wheel 17 May 15 10:22 python3.6-config ->
>> python3.6m-config
>>>> -r-xr-xr-x 2 root wheel 15392 May 15 10:21 python3.6m
>>>> -r-xr-xr-x 1 root wheel 3127 May 15 10:22 python3.6m-config
>>>> -r-xr-xr-x 2 root wheel 15208 Apr 23 03:20 python3.7
>>>> lrwxr-xr-x 1 root wheel 17 Apr 23 03:20 python3.7-config ->
>> python3.7m-config
>>>> -r-xr-xr-x 2 root wheel 15208 Apr 23 03:20 python3.7m
>>>> -r-xr-xr-x 1 root wheel 2936 Apr 23 03:20 python3.7m-config
>>>> -rwxr-xr-x 1 root wheel 441 May 15 10:22 pyvenv-3.6
>>>> -rwxr-xr-x 1 root wheel 441 Apr 23 03:20 pyvenv-3.7
>>>>
>>>>> The same advice applies to lang/python2 and lang/python3, if any of
>>>>> these are installed.
>>>>>
>>>>> Just a friendly piece of advice:
>>>>>
>>>>> Explore the possible use of ports-mgmt/poudriere and ports-mgmt/synth.
>>>>> Even an old fart like myself have realised their potential and
>>>>> practical value.
>>>>>
>>>>> They both build each package in full isolation from the running system
>>>>> and from each other. They can also build packages in parallel.
>>>>>
>>>>> synth is more straight forward of the two but requires an Ada
>>>>> compiler. Its /usr/local/etc/synth/synth.ini has self-explanatory
>>>>> parameters for each profile you create.
>>>>>
>>>>> poudriere requires you to set ALLOW_MAKE_JOBS=yes and PARALLEL_JOBS=6
>>>>> in /usr/local/etc/poudriere.conf, and MAKE_JOBS_NUMBER=4 in
>>>>> /usr/local/etc/poudriere.d/make.conf, in order to achieve reasonable
>>>>> parallelism.
>>>>>
>>>>> 6 and 4 are the values chosen by synth when auto-configured on an
>>>>> 8-core system, yielding a 300 % load on the CPUs in the worst case.
>>>>> Adjust these values to suit your system and/or taste.
>>>>
>>>> # dmesg | head
>>>> ---<<BOOT>>---
>>>> Copyright (c) 1992-2019 The FreeBSD Project.
>>>> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
>>>> The Regents of the University of California. All rights reserved.
>>>> FreeBSD is a registered trademark of The FreeBSD Foundation.
>>>> FreeBSD 12.1-RELEASE GENERIC amd64
>>>> FreeBSD clang version 8.0.1 (tags/RELEASE_801/final 366581) (based on
>> LLVM 8.0.1)
>>>> VT(vga): resolution 640x480
>>>> CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ (1995.64-MHz
>> K8-class CPU)
>>>> Origin="AuthenticAMD" Id=0x20fb1 Family=0xf Model=0x2b Stepping=1
>>>> #
>>>>
>>>>
>>>> I’m afraid there is not much to parallelize :( (with a dual core)
>>>
>>> Incidently, I'm playing with an old Dell Latitude D531 at $WORK. It
>>> has almost the same processor as your system. It took me 84 hours
>>> building stable/11 from scratch. synth ran for 8 days and 17 hours
>>> while building in excess of 700 packages. synth initially ran in a 2x2
>>> configuration, but I'm now experimenting running it as 1x2. I have two
>>> separate ccache instances, one for each of base and localbase, at
>>> least it speeds up autoconf and friends.
>>>
>>> --
>>> Trond.
>>
>>
> Here is a snippet from virtualbox-ose's Makefile:
>
> .if ${PORT_OPTIONS:MPYTHON}
> USES+= python:2.7
> USE_PYTHON= distutils noegginfo noflavors
> PYDISTUTILS_PKGNAME= vboxapi
> PYDISTUTILS_PKGVERSION= 1.0
> .else
> USES+= python:2.7,build
> .endif
>
> Virtualbox itself asks for it.
>
> As an experiment, I switched both lines for python:3.7 and compiled the
> port.
>
> The port builds without errors and VirtualBox runs just fine.
>
> --
> Mario Lobo
> http://www.mallavoodoo.com.br <http://www.mallavoodoo.com.br/>
> FreeBSD since version 2.2.8 [not Pro-Audio.... YET!!]
> _______________________________________________
> freebsd-questions at freebsd.org <mailto:freebsd-questions at freebsd.org> mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-questions <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org <mailto:freebsd-questions-unsubscribe at freebsd.org>"
More information about the freebsd-questions
mailing list