It looks like the source tree has copies of itself inside it. This part of
the path is repeating:
/racket/pipo/app/lib/plt/tlf/exts/ert/r0/
I use raco distribute regularly on Windows, and while the path tree it
creates is longer than I would like, it is nowhere near as deep, here is
mine from a simple GUI application:
$ find . -type d -print
.
./lib
./lib/plt
./lib/plt/AL2-IRisk
./lib/plt/AL2-IRisk/exts
./lib/plt/AL2-IRisk/exts/ert
./lib/plt/AL2-IRisk/exts/ert/r0
./lib/plt/AL2-IRisk/exts/ert/r1
./lib/plt/AL2-IRisk/exts/ert/r2
./lib/plt/AL2-IRisk/exts/ert/r2/scribble
./lib/plt/AL2-IRisk/exts/ert/r3
./lib/plt/AL2-IRisk/exts/ert/r3/bundles
./lib/plt/AL2-IRisk/exts/ert/r3/bundles/es
./lib/plt/AL2-IRisk/exts/ert/r4
Here are a few things you can try:
* write a simple "hello world" racket program and use raco distribute on it
to see if the same problem happen
* might be worth cloning your source repo into a new location and try
building it again
* check if you have any symbolic or hard links in your source tree
Alex.
On Saturday, February 9, 2019 at 6:26:02 AM UTC+8, P. Baillet wrote:
>
> Hello list,
>
> I’ve been playing with raco distribute to build small docker images with
> racket binaries in them and it seems that the command sometimes creates a
> very deep tree and crashes in the end (with Racket 7.2):
>
> root@a8ec24e4167d:/racket/pipo# raco distribute app tlf
> copy-file: cannot open destination file
> source path:
> /racket/pipo/app/lib/plt/tlf/exts/ert/r0/racket/pipo/app/lib/plt/tlf/exts/ert/r0/racket/pipo/app/lib/plt/tlf/exts/ert/r0/racket/pipo/app/lib/plt/tlf/exts/ert/r0/racket/pipo/app/lib/plt/tlf/exts/ert/r0/racket/pipo/app/lib/plt/tlf/exts/ert/r0/racket/pi...
> destination path:
> /racket/pipo/app/lib/plt/tlf/exts/ert/r0/racket/pipo/app/lib/plt/tlf/exts/ert/r0/racket/pipo/app/lib/plt/tlf/exts/ert/r0/racket/pipo/app/lib/plt/tlf/exts/ert/r0/racket/pipo/app/lib/plt/tlf/exts/ert/r0/racket/pipo/app/lib/plt/tlf/exts/ert/r0/racket/pi...
> system error: File name too long; errno=36
> context...:
> /usr/share/racket/collects/racket/file.rkt:94:2: loop
> /usr/share/racket/collects/racket/private/map.rkt:68:13: for-each
> /usr/share/racket/collects/racket/file.rkt:94:2: loop
> /usr/share/racket/collects/racket/private/map.rkt:68:13: for-each
> /usr/share/racket/collects/racket/file.rkt:94:2: loop
> /usr/share/racket/collects/racket/private/map.rkt:68:13: for-each
> /usr/share/racket/collects/racket/file.rkt:94:2: loop
> /usr/share/racket/collects/racket/private/map.rkt:68:13: for-each
> /usr/share/racket/collects/racket/file.rkt:94:2: loop
> /usr/share/racket/collects/racket/private/map.rkt:68:13: for-each
> /usr/share/racket/collects/racket/private/map.rkt:74:19: loop
> /usr/share/racket/collects/racket/private/map.rkt:68:13: for-each
> /usr/share/racket/collects/racket/file.rkt:94:2: loop
> /usr/share/racket/collects/racket/private/map.rkt:68:13: for-each
> /usr/share/racket/collects/racket/file.rkt:94:2: loop
> /usr/share/racket/collects/racket/private/map.rkt:68:13: for-each
> ...
>
> For a while, I thought this was because I was in /tmp, but further
> experiments showed that it also happened in other places. I tried moving my
> binary in another place before running distribute on it but it can also
> fails because the distribute code is trying to read things where I built
> the app(?).
>
> Any idea on how to workaround this issue?
>
> —
> P.
>
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
