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 ?
I just tested installing a cvs fresh 7.5 compiled with --with-relocatable-dumped-modules and it seems to work. I could move the installed tree if I just updated the absolute paths in master.pike and in the pike binary.
/ Martin Stjernholm, Roxen IS
Previous text:
2003-12-20 19:22: Subject: How to dump pike modules in a fakeroot/sandbox environment?
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 ?
-- Rainer Groesslinger rainer.groesslinger@gmx.net
/ Brevbäraren
I just noticed today, that the reference to the fakeroot seems to be caused by the .o files. But as far as I know (please correct me) after make install is complete *.o files are not needed anymore ? so
rm -vf `find . -regex '.*.o' -type f | xargs`
seems to solve my problem. All decode errors are gone now, is there a reason why the .o files should be kept ?
Thank you again for your help.
Martin Stjernholm, Roxen IS wrote:
I just tested installing a cvs fresh 7.5 compiled with --with-relocatable-dumped-modules and it seems to work. I could move the installed tree if I just updated the absolute paths in master.pike and in the pike binary.
/ Martin Stjernholm, Roxen IS
You're mistaken. The sole purpose of the .o files is to remain so that modules are loaded faster when pike is started. You can easily see the difference in startup time if you remove them.
It seems to me like the relocation setting disappears for you somewhere along the way. As I said, it works for me and I get no references to the fakeroot path except in lib/master.pike, lib/master.pike.o and bin/pike.
/ Martin Stjernholm, Roxen IS
Previous text:
2003-12-21 18:44: Subject: Re: How to dump pike modules in a fakeroot/sandbox environment?
I just noticed today, that the reference to the fakeroot seems to be caused by the .o files. But as far as I know (please correct me) after make install is complete *.o files are not needed anymore ? so
rm -vf `find . -regex '.*.o' -type f | xargs`
seems to solve my problem. All decode errors are gone now, is there a reason why the .o files should be kept ?
Thank you again for your help.
Martin Stjernholm, Roxen IS wrote:
I just tested installing a cvs fresh 7.5 compiled with --with-relocatable-dumped-modules and it seems to work. I could move the installed tree if I just updated the absolute paths in master.pike and in the pike binary.
/ Martin Stjernholm, Roxen IS
-- Rainer Groesslinger rainer.groesslinger@gmx.net
/ Brevbäraren
Are you both using CVS versions of 7.5? I thought the problem was originally with 7.4...
Bill
On Sunday, December 21, 2003, at 12:50 PM, Martin Stjernholm, Roxen IS @ Pike developers forum wrote:
You're mistaken. The sole purpose of the .o files is to remain so that modules are loaded faster when pike is started. You can easily see the difference in startup time if you remove them.
It seems to me like the relocation setting disappears for you somewhere along the way. As I said, it works for me and I get no references to the fakeroot path except in lib/master.pike, lib/master.pike.o and bin/pike.
/ Martin Stjernholm, Roxen IS
I've now tested with 7.4 too and it works equally well there.
/ Martin Stjernholm, Roxen IS
Previous text:
2003-12-21 19:04: Subject: Re: How to dump pike modules in a fakeroot/sandbox environment?
Are you both using CVS versions of 7.5? I thought the problem was originally with 7.4...
Bill
On Sunday, December 21, 2003, at 12:50 PM, Martin Stjernholm, Roxen IS @ Pike developers forum wrote:
You're mistaken. The sole purpose of the .o files is to remain so that modules are loaded faster when pike is started. You can easily see the difference in startup time if you remove them.
It seems to me like the relocation setting disappears for you somewhere along the way. As I said, it works for me and I get no references to the fakeroot path except in lib/master.pike, lib/master.pike.o and bin/pike.
/ Martin Stjernholm, Roxen IS
/ Brevbäraren
pike-devel@lists.lysator.liu.se
-
Bill Welliver -
Martin Stjernholm, Roxen IS ＠ Pike developers forum -
Rainer Groesslinger