Martin Stjernholm, Roxen IS wrote:
If the files aren't moved to another location, how can it become a problem that the pike binary wants to load [/my/fakeroot/path]/lib/master.pike?
I am sorry I misunderstood you there. Of course they are moved from the virtual /usr (= /fakeroot/usr) to the real /usr after 'make INSTALLARGS="--traditional" buildroot="/fakeroot" install' completed. (Before that, I use make CONFIGUREARGS="--prefix=/usr --disable-make_conf \ --with-relocatable-dumped-modules")
As you suggested I looked at PIKE_MODULE_RELOC and I also found out about the configure param called "--with-relocatable-dumped-modules" but it doesn't seem to change anything :(
I still have the problem that pike is being built in a working directory, then installed to /fakeroot/usr (given /usr as the --prefix and /fakeroot as the buildroot) and after that process is complete, it is moved to the real /usr/...
Even if I try to set PIKE_MODULE_RELOC (or use --with-relocatable-dumped-modules) some modules still look in /fakeroot/usr/...
(some work, but Regex doesn't and if I run e.g. 'pike --features' also Yp among a few others give me a decode warning referencing to /fakeroot/usr/...)
Perhaps I missed something or I am using --with-relocatable-dumped-modules the wrong way ?