[MacPorts] #62994: various ports fail to install on Leopard due to gnulib issue: /confdir-14B---: No space left on device

[MacPorts]

#62994: various ports fail to install on Leopard due to gnulib issue: /confdir-
14B---: No space left on device
---------------------------------------------------+----------------------
  Reporter:  kencu                                 |      Owner:  mascguy
      Type:  defect                                |     Status:  assigned
  Priority:  Normal                                |  Milestone:
 Component:  ports                                 |    Version:
Resolution:                                        |   Keywords:  leopard
      Port:  m4 bison findutils coreutils gettext  |
---------------------------------------------------+----------------------

Comment (by fhgwright):

 Replying to [comment:127 kencu]:
 > so that directory shouldn't have even been created -- which leads me to
 ponder that it might be left behind / left over from some previous attempt
 to build this.
 >
 > can you {{{sudo port clean coreutils}}}
 >
 > then go into the directory and make sure eveything is gone:
 > {{{
 > cd `port dir coreutils`
 > ls
 > }}}
 >
 > and if you still see a work directory in there, remove it using "grm"
 which was noted above to be capable of removing this deep directory.

 Using `port dir coreutils` only works if the work directory is under the
 port directory, which AFAIK is only true if one used the "omitted portname
 kludge" to attempt the build in the first place.

 > now -- catch 22 -- you can't use "grm" unless you have installed
 coreutils already .... so what I did was
 >
 > {{{
 > sudo rm -rf work
 > }}}
 >
 > about 10 times and it seemed to finally get rid of the directory...

 What I found works is:
 {{{
 cd $(port work <portname>)
 sudo mv .../<some deeper directory> .
 sudo rm -rf <some deeper directory>
 cd -
 sudo port clean <portname>
 }}}
 I.e., it looks like a single `mv` of a subtree to a shallower depth is
 sufficient to make `rm -rf` work.  The explicit `rm -rf` might not even be
 necessary, since the `mv` alone might be sufficient to make `port clean`
 work.

 Note that if you haven't been consistent about whether you're using the
 "omitted portname kludge" or not, then you may need to do the above twice,
 with and without the kludge.

-- 
Ticket URL: <https://trac.macports.org/ticket/62994#comment:128>
MacPorts <https://www.macports.org/>
Ports system for macOS