[MacPorts] #50567: findutils 4.6.0 cannot be installed on PPC Mac OS X 10.5.8, Leopard, because of strange directory name confdir-14B---

[MacPorts]

#50567: findutils 4.6.0 cannot be installed on PPC Mac OS X 10.5.8, Leopard,
because of strange directory name confdir-14B---
------------------------------+--------------------------------
  Reporter:  Peter_Dyballa@…  |      Owner:  macports-tickets@…
      Type:  defect           |     Status:  new
  Priority:  Normal           |  Milestone:
 Component:  ports            |    Version:  2.3.4
Resolution:                   |   Keywords:
      Port:  findutils        |
------------------------------+--------------------------------

Comment (by Peter_Dyballa@…):

 Replying to [comment:9 Peter_Dyballa@…]:
 > Replying to [comment:7 ryandesign@…]:
 > >
 > I'll try to discuss the GNU Emacs case with its developers!

 No necessity for this (excerpt from `sudo port -dkv clean findutils`):

 {{{
 --->  Cleaning findutils
 DEBUG: Executing org.macports.clean (findutils)
 --->  Removing work directory for findutils
 DEBUG: Removing directory:
 /opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_sysutils_findutils/findutils
 DEBUG: error deleting
 "/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_sysutils_findutils/findutils/work/findutils-4.6.0
 /confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B
 ---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-
 14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B
 ---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-
 14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B
 ---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-
 14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B
 ---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-
 14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B
 ---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-
 14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B
 ---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-
 14B---/confdir-14B---/confdir-14B---": file name too long
     while executing
 "file delete -force -- {*}$args"
     (procedure "delete" line 2)
     invoked from within
 "delete $subbuildpath"
 Error: error deleting
 "/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_sysutils_findutils/findutils/work/findutils-4.6.0
 /confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B
 ---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-
 14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B
 ---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-
 14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B
 ---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-
 14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B
 ---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-
 14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B
 ---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-
 14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B
 ---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-14B---/confdir-
 14B---/confdir-14B---/confdir-14B---": file name too long
 DEBUG: No work directory found to remove at
 /Users/pete/.macports/opt/local/var/macports/build/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_sysutils_findutils/findutils
 DEBUG: No log directory found to remove at
 /opt/local/var/macports/logs/_opt_local_var_macports_sources_nue.de.rsync.macports.org_macports_release_tarballs_ports_sysutils_findutils
 DEBUG: Checking time since last reclaim run
 }}}

 So this too long path names are built anyway and in Terminal `port` has
 also the problems to avoid them and to remove them.

 Before I try to find the cause for this "No space left on device" message:
 is it possible to make `port` add a time stamp to its info verbose debug
 output? I had (t)csh perform inside ann endless while loop

 {{{
 date "+%F %T" | tr '\012' '     ' ; df -h | egrep '/$'
 sleep 1
 }}}

 so that I could see for every second of the build process that I had 7,2
 GiB of free space. It would be nice to correlate the time of the "No space
 left on device" message with a disk free report.

-- 
Ticket URL: <https://trac.macports.org/ticket/50567#comment:10>
MacPorts <https://www.macports.org/>
Ports system for OS X