I'm trying to build dev-python/setuptools-5.7 and the install phase fails. This is within a f2fs image running under qemu. (ARM emulation) I understand this is not a common setup. However I suspect the issue stems from a missing file locking function (or something similar related to the filesystem) in f2fs. writing manifest file '/var/tmp/portage/dev-python/setuptools-5.7/work/setuptools-5.7-python3_4/build/setuptools.egg-info/SOURCES.txt' Copying /var/tmp/portage/dev-python/setuptools-5.7/work/setuptools-5.7-python3_4/build/setuptools.egg-info to /var/tmp/portage/dev-python/setuptools-5.7/image//_python3.4/usr/lib/python3.4/site-packages/setuptools-5.7-py3.4.egg-info error: [Errno 38] Function not implemented: '/var/tmp/portage/dev-python/setuptools-5.7/work/setuptools-5.7-python3_4/build/setuptools.egg-info/dependency_links.txt' Reproducible: Always
Please attach a full build log. Also, it would help if you could do a bit more debugging yourself. We would just be guessing at where the problem is occurring. I suspect it is somewhere in setuptools.archive_util.unpack_directory(). If you insert some debug print statements in /usr/lib/python3.4/setuptools/archive_util.py to confirm that and possibly narrow it down, that would be helpful.
Created attachment 384182 [details] Build Log
There currently is no such file /usr/lib/python3.4/setuptools/archive_util.py Or perhaps did you mean relative to the working directory? The existing setuptools version is quite old (1.1.6) and was not built with python 3.4 support. Currently existing paths for that archive_util.py are: /usr/lib/python2.7/distutils/archive_util.py /usr/lib/python2.7/distutils/archive_util.pyc /usr/lib/python2.7/distutils/archive_util.pyo /usr/lib/python2.7/distutils/tests/test_archive_util.py /usr/lib/python2.7/distutils/tests/test_archive_util.pyc /usr/lib/python2.7/distutils/tests/test_archive_util.pyo /usr/lib/python2.7/site-packages/setuptools/archive_util.py /usr/lib/python2.7/site-packages/setuptools/archive_util.pyc /usr/lib/python2.7/site-packages/setuptools/archive_util.pyo /usr/lib/python3.2/distutils/archive_util.py /usr/lib/python3.2/distutils/tests/test_archive_util.py /usr/lib/python3.2/site-packages/setuptools/archive_util.py /usr/lib/python3.3/distutils/archive_util.py /usr/lib/python3.3/distutils/tests/test_archive_util.py /usr/lib/python3.3/site-packages/setuptools/archive_util.py /usr/lib/python3.4/distutils/archive_util.py /usr/lib/python3.4/distutils/tests/test_archive_util.py /var/tmp/portage/dev-python/setuptools-5.7/image/_python3.3/usr/lib/python3.3/site-packages/setuptools/archive_util.py /var/tmp/portage/dev-python/setuptools-5.7/image/_python3.4/usr/lib/python3.4/site-packages/setuptools/archive_util.py /var/tmp/portage/dev-python/setuptools-5.7/image/usr/lib/python2.7/site-packages/setuptools/archive_util.py /var/tmp/portage/dev-python/setuptools-5.7/image/usr/lib/python2.7/site-packages/setuptools/archive_util.pyc /var/tmp/portage/dev-python/setuptools-5.7/image/usr/lib/python2.7/site-packages/setuptools/archive_util.pyo /var/tmp/portage/dev-python/setuptools-5.7/work/setuptools-5.7/setuptools/archive_util.py /var/tmp/portage/dev-python/setuptools-5.7/work/setuptools-5.7-python2_7/build/lib/setuptools/archive_util.py /var/tmp/portage/dev-python/setuptools-5.7/work/setuptools-5.7-python2_7/setuptools/archive_util.py /var/tmp/portage/dev-python/setuptools-5.7/work/setuptools-5.7-python2_7/setuptools/archive_util.pyc /var/tmp/portage/dev-python/setuptools-5.7/work/setuptools-5.7-python3_3/build/lib/setuptools/archive_util.py /var/tmp/portage/dev-python/setuptools-5.7/work/setuptools-5.7-python3_3/setuptools/archive_util.py /var/tmp/portage/dev-python/setuptools-5.7/work/setuptools-5.7-python3_4/build/lib/setuptools/archive_util.py /var/tmp/portage/dev-python/setuptools-5.7/work/setuptools-5.7-python3_4/setuptools/archive_util.py I'll probably need direction in what I'm looking for. I'm not very familiar with python.
This isn't a support forum. When you find the actual bug, then please reopen this bug report with appropriate information.
Meh. There are just too many locking (and other) syscalls that are not yet supported on this file system. I created a small ext4 image and mounted it to /var/tmp/portage to work around it. It's a hack but it works. As it is a limitation of the file system itself, and is not officially one of the filesystems supported for a system install, it's probably not something Gentoo should be trying to fix.
