Re: x11/nvidia-driver build failed at devel/py-importlib-metadata
- In reply to: Tomoaki AOKI : "Re: x11/nvidia-driver build failed at devel/py-importlib-metadata"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 21 Jun 2023 13:19:34 UTC
On Wed, 21 Jun 2023 22:08:59 +0900, Tomoaki AOKI wrote: > > On Wed, 21 Jun 2023 20:37:56 +0900 > KIRIYAMA Kazuhiko <kiri@truefc.org> wrote: > > > Hi, list > > > > x11/nvidia-driver build failed at devel/py-importlib-metadata: > > > > Copying importlib_metadata.egg-info to /var/ports/work/var/ports/msrvkx/devel/py-importlib-metadata/work-py39/stage/usr/local/lib/python3.9/site-packages/importlib_metadata-2.0.0-py3.9.egg-info > > running install_scripts > > writing list of installed files to '/var/ports/work/var/ports/msrvkx/devel/py-importlib-metadata/work-py39/.PLIST.pymodtmp' > > ====> Compressing man pages (compress-man) > > ===> Installing for py39-importlib-metadata-2.0.0 > > ===> Checking if py39-importlib-metadata is already installed > > ===> Registering installation for py39-importlib-metadata-2.0.0 as automatic > > Installing py39-importlib-metadata-2.0.0... > > ===> py39-markdown-3.3.7 depends on package: py39-importlib-metadata>=4.4 - not found > > *** Error code 1 > > > > Stop. > > make[5]: stopped in /var/ports/msrvkx/textproc/py-markdown > > *** Error code 1 > > > > Stop. > > make[4]: stopped in /var/ports/msrvkx/textproc/py-sphinx-markdown-tables > > *** Error code 1 > > > > Stop. > > make[3]: stopped in /var/ports/msrvkx/devel/llvm15 > > *** Error code 1 > > > > Stop. > > make[2]: stopped in /var/ports/msrvkx/graphics/mesa-dri > > *** Error code 1 > > > > Stop. > > make[1]: stopped in /var/ports/msrvkx/x11-servers/xorg-server > > *** Error code 1 > > > > Stop. > > make: stopped in /usr/ports/x11/nvidia-driver > > > > Is there any suggetions? > > > > My build environments are: > > > > root@msrvkx:~ # uname -a > > FreeBSD msrvkx 14.0-CURRENT FreeBSD 14.0-CURRENT #0 n263415-9d6ae1e3c26a-dirty: Sat Jun 17 05:50:51 JST 2023 root@msrvkx:/usr/obj/usr/src/amd64.amd64/sys/XIJ amd64 > > root@msrvkx:~ # cat /etc/make.conf > > PORTSDIR= /var/ports/msrvkx > > INDEXDIR= /var/ports/msrvkx > > WRKDIRPREFIX= /var/ports/work > > PACKAGES= /var/ports/packages > > DISTDIR= /var/ports/distfiles > > BATCH= yes > > DEFAULT_VERSIONS= perl5=5.36 ruby=3.3 > > COMPILER_TYPE= clang > > USE_PACKAGE_DEPENDS= yes > > DISABLE_VULNERABILITIES=yes > > root@msrvkx:~ # df -h > > Filesystem Size Used Avail Capacity Mounted on > > /dev/vtbd0p2 59G 9.4G 45G 17% / > > devfs 1.0K 0B 1.0K 0% /dev > > linprocfs 8.0K 0B 8.0K 0% /compat/linux/proc > > tmpfs 3.2G 4.0K 3.2G 0% /compat/linux/dev/shm > > linsysfs 8.0K 0B 8.0K 0% /compat/linux/sys > > devfs 1.0K 0B 1.0K 0% /compat/linux/dev > > fdescfs 1.0K 0B 1.0K 0% /compat/linux/dev/fd > > vm.tfc:/.dake 11T 1.1T 9.8T 10% /.dake > > vm.tfc:/ds/src/freebsd/current/14.0/9d6ae1e3c26a.xij 9.9T 77G 9.8T 1% /usr/src > > vm.tfc:/ds/obj/freebsd/current/14.0/9d6ae1e3c26a.xij 10T 407G 9.8T 4% /usr/obj > > vm.tfc:/ds/ports/freebsd/d830ac4c7cfd 9.9T 129G 9.8T 1% /usr/ports > > vm.tfc:/ds/distfiles 9.9T 63G 9.8T 1% /var/ports/distfiles > > vm.tfc:/ds/packages/freebsd/amd64/amd64/14.0C/9d6ae1e3c26a.xij/d830ac4c7cfd 9.9T 128G 9.8T 1% /var/ports/packages > > root@msrvkx:~ # > > > > root@vm:~ # git -C /ds/ports/freebsd/d830ac4c7cfd rev-parse --verify --short HEAD > > d830ac4c7cfd > > root@vm:~ # > > > > I tried to change Python version as: > > > > root@msrvkx:~ # cat /etc/make.conf.bak > > PORTSDIR= /var/ports/msrvkx > > INDEXDIR= /var/ports/msrvkx > > WRKDIRPREFIX= /var/ports/work > > PACKAGES= /var/ports/packages > > DISTDIR= /var/ports/distfiles > > BATCH= yes > > DEFAULT_VERSIONS= perl5=5.36 python3=3.8 ruby=2.7 > > COMPILER_TYPE= clang > > USE_PACKAGE_DEPENDS= yes > > DISABLE_VULNERABILITIES=yes > > root@msrvkx:~ # > > > > > > But bsd.ports.mk complains: > > > > /!\ WARNING /!\ > > > > PYTHON_DEFAULT must be a version present in PYTHON2_DEFAULT or PYTHON3_DEFAULT, > > if you want more Python flavors, set BUILD_ALL_PYTHON_FLAVORS in your make.conf > > > > and could not changed ;-( > > > > Best regards > > --- > > Kazuhiko Kiriyama <kiri@truefc.org> > > > > What about /etc/make.conf? > The file you mentioned is /etc/make.conf.bak, and should not at all > processed unless you explicitly include it from /etc/make.conf (or > manually specify at command line). Sorry, that's typo. s/make.conf.bak/make.conf/ :-) --- Kazuhiko Kiriyama