Hi,
I am having a problem building pike in a fakeroot/sandbox'ed environment and *additionally* dump the pike modules.
(to avoid those problems you surely have heard about hundred times when building in a fakeroot and then try to run a pike application using a module: /usr/lib/pike/.../.../whatever.pmod.o:-: Warning: Decode failed: Failed to decode program)
The problem I am having is, pike seems to be able to dump the modules when installing in a fakeroot environment from what I can read in the install scripts but it cannot do it without violating the sandbox (e.g. writing outside the fakeroot).
In short, I do the following (after pike was built using make CONFIGUREARGS="..." etc.):
sed -i s/rm(mod+".o");/{}/ for install.pike, which results in the following:
--- install.pike.orig +++ install.pike @@ -1096,7 +1096,7 @@ rm("dumpmodule.log");
foreach(to_dump, string mod) - rm(mod+".o"); + {}
// Dump 25 modules at a time
I need to do this, because otherwise the sandbox is violated since pike directly wants to do some action in /usr/lib/...
Then I use the following command to install pike:
make INSTALLARGS="--traditional" buildroot="${D}" install
("${D}" being the virtual "/") Because of the change to install.pike, the modules aren't dumped automagically, and to be honest, I feel a bit lost now how I can dump the modules to avoid those fakeroot/decode problems with the modules, but without violating the sandbox.
Thanks in advance for your answers,