[MacPorts] #62994: various ports fail to install on Leopard due to gnulib issue: /confdir-14B---: No space left on device
MacPorts
noreply at macports.org
Sun May 7 06:53:21 UTC 2023
#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 |
-------------------------------------------+----------------------
Comment (by ballapete):
The question should be: Why is it possible to create a pathname that is
too long to handle it afterwards, after creation? So that `rm` cannot
handle it? Which is the final failure.
(Actually `mv` still can handle this 'out of limits' pathname somehow, for
example move the last and deepest directory to /tmp and shorting the
pathname by 14 or 15 characters that `rm` can remove the whole directory
structure.)
In my tests, years ago, I modified the `configure` script to create
subdirectories with shorter or longer names (by adding or removing HYPHEN-
MINUS) and printing out the length of the pathname to be created. It could
become longer than PATH_MAX = 1024.
The reason why it fails or not is that the directory structure starts with
varying bias, because the working directory where `configure` starts from
has variable length depending on the length of the utility's name and the
length of the rsync server's name, the category of software, and possibly
the starting point of MacPorts (it can be different from /opt or
/opt/local, can't it?).
--
Ticket URL: <https://trac.macports.org/ticket/62994#comment:55>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list