At least I haven't seen that problem a hundred times. I can imagine there are problems if pike is installed in one location, tar'ed together and then extracted in a different place. That's because absolute paths normally are written in the dumped files, and that the pike binary is modified to contain an absolute path to the master.
and that is my problem, but see below. (btw. "a hundred times" may a bit overkill but I found a few messages about it in the archives and also google had some results on this problem)
(The NT installation variant contains relocation code to avoid absolute paths since, if I remember correctly, modules can't be dumped at installation time for some reason. Anyway, that stuff doesn't work entirely well.)
I don't understand how your fix solves anything. If the files that pike tries to remove there are in the wrong place then the dumping later on will fail much more, and pretty much the whole setup of the installed tree too, I suspect.
It looks rather like the install prefix to install.pike is incorrect. You can control it with an argument prefix=a/good/place to the installer.
I am already using prefix... The problem is this: If I use prefix=/usr and build it pike violates the sandbox because it directly wants to dump in /usr/... that's why I modify install.pike. If I use [/my/fakeroot/path]/usr as a prefix and keep install.pike as it is, dumping the module works, but the pike binary doesn't because it wants to run [/my/fakeroot/path]/.../pike which afterwards, of course, doesn't exist anymore. (and if it still does, that's not a satisfying solution either ;)
So my problem with pike and a fakeroot/sandbox environment is in other words: 1. I can only solve the sandbox issue by modifying install.pike (like shown in my original mail) but then the modules aren't dumped and thus, don't work, or 2. only fix the module problem by using the virtual path + /usr as the prefix, dumping the modules works then, but e.g. the pike binary is still referencing to the virtual builddir.
But I can't find a solution to solve both. (Note: The files are *not* tar'ed and moved to another location/system or whatever, everybody using fakeroot+sandbox has that problem, I just can't find a solution for it).
btw. "buildroot" was the virtual path in all cases.