[Buildd-tools-devel] Bug#483350: Bug#483350: pperl: FTBFS: pperl: perl script failed to start: No such file or directory

[Florian Weimer]

* Roger Leigh:

> So, from what I understand of the report, pperl is creating a UNIX
> domain socket during its build, and the pathname is too long.

Correct.

> /build/user-pperl_0.25-5-amd64-0uuJx5/pperl-0.25-5/sockets/pperlnPLXc7
> /build/pperl-0.25-5/sockets/pperlnPLXc7
>
> That's 71 and 40 chars respectively (including NUL terminator if
> needed).  I don't see either as being excessively long.  Is this really
> what caused the failure, or is something else going on here?  We're
> nowhere near exceeding UNIX_PATH_MAX.

pperl uses an escaped form of the script name (which again resides in
the build directory) as the file name component of the socket, crossing
over the 109 character limit as a result.  As I wrote in the bug report,
I think this is an issue with pperl which should be fixed.  However,
with 70sh characters in the path and a base16 encoding of a 128-bit
hash, this still leaves us very close to the limit.