The long paths are not a MacPorts specific issue
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750231
On 10/11/14 08:20, Nicolas Pavillon wrote:
Hello,
It's been some time, but I had tried to make a Portfile for pykde4, and
then gave up because of several different issues, including the
dependencies to X11. These repeated paths also surely ring a bell. I
don't think I ever got around them, but did not try that hard either.
Cheers,
Nicolas
On 10/11/2014 16:08, Ryan Schmidt wrote:
On Nov 9, 2014, at 12:04 PM, René J.V. Bertin wrote:
Has anyone tried his/her hand at a Portfile for PyKDE4, with success?
I'm doing just that, but one of the blocks I'm running into has to do
with MacPort's convoluted naming for build directories:
-- Configuring done
CMake Error: Cannot open file for write:
/Volumes/Debian/MP6/var/macports/build/_Volumes_Debian_MP6_site-ports_kde_py-pykde4/py33-pykde4/work/build/CMakeFiles/_Volumes_Debian_MP6_var_macports_build__Volumes_Debian_MP6_site-ports_kde_py-pykde4_py33-pykde4_work_build__Volumes_Debian_MP6_var_macports_build__Volumes_Debian_MP6_site-ports_kde_py-pykde4_py33-pykde4_work_build__Volumes_Debian_MP6_var_macports_build__Volumes_Debian_MP6_site-ports_kde_py-pykde4_py33-pykde4_work_build___pycache___pykdeconfig.cpython-33.pyc.dir/build.make.tmp
CMake Error: : System Error: File name too long
CMake Error: Could not create
/Volumes/Debian/MP6/var/macports/build/_Volumes_Debian_MP6_site-ports_kde_py-pykde4/py33-pykde4/work/build/CMakeFiles/_Volumes_Debian_MP6_var_macports_build__Volumes_Debian_MP6_site-ports_kde_py-pykde4_py33-pykde4_work_build__Volumes_Debian_MP6_var_macports_build__Volumes_Debian_MP6_site-ports_kde_py-pykde4_py33-pykde4_work_build__Volumes_Debian_MP6_var_macports_build__Volumes_Debian_MP6_site-ports_kde_py-pykde4_py33-pykde4_work_build___pycache___pykdeconfig.cpython-33.pyc.dir/cmake_clean.cmake
CMake Error: Cannot open file for write:
/Volumes/Debian/MP6/var/macports/build/_Volumes_Debian_MP6_site-ports_kde_py-pykde4/py33-pykde4/work/build/CMakeFiles/_Volumes_Debian_MP6_var_macports_build__Volumes_Debian_MP6_site-ports_kde_py-pykde4_py33-pykde4_work_build__Volumes_Debian_MP6_var_macports_build__Volumes_Debian_MP6_site-ports_kde_py-pykde4_py33-pykde4_work_build__Volumes_Debian_MP6_var_macports_build__Volumes_Debian_MP6_site-ports_kde_py-pykde4_py33-pykde4_work_build___pycache___pykdeconfig.cpython-33.pyc.dir/DependInfo.cmake.tmp
CMake Error: : System Error: File name too long
-- Generating done
CMake Error: Cannot open file for write:
/Volumes/Debian/MP6/var/macports/build/_Volumes_Debian_MP6_site-ports_kde_py-pykde4/py33-pykde4/work/build/CMakeFiles/_Volumes_Debian_MP6_var_macports_build__Volumes_Debian_MP6_site-ports_kde_py-pykde4_py33-pykde4_work_build__Volumes_Debian_MP6_var_macports_build__Volumes_Debian_MP6_site-ports_kde_py-pykde4_py33-pykde4_work_build__Volumes_Debian_MP6_var_macports_build__Volumes_Debian_MP6_site-ports_kde_py-pykde4_py33-pykde4_work_build___pycache___pykdeconfig.cpython-33.pyc.dir/progress.make.tmp
CMake Error: : System Error: File name too long
Grr!
The path shown above seems to have unnecessarily repeated bits. Do you
perhaps have some kind of recursive symlink problem going on? What is
causing the very long names in the build/CMakeFiles directory? Surely
it's pykde4's build system that's responsible for anything happening
in there. Or perhaps something you're doing in your portfile; hard to
say since I haven't seen your portfile.
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
