[pg-cvs] Bad interaction with SB-EXT:SAVE-LISP-AND-DIE
When I create a custom core the location of libosicat.so is hard-coded in the binary. Osicat should instruct CFFI/SB-ALIEN to load this library with :DONT-SAVE T to prevent saving a fixed path. Leslie -- http://www.linkedin.com/in/polzer
"Leslie P. Polzer" <sky@viridian-project.de> writes:
When I create a custom core the location of libosicat.so is hard-coded in the binary.
Osicat should instruct CFFI/SB-ALIEN to load this library with :DONT-SAVE T to prevent saving a fixed path.
This a problem we're tackling in CFFI. For now, the best thing you can do is explicitly unload libosicat.so before saving the core, then reload it in an init hook. -- Luís Oliveira http://student.dei.uc.pt/~lmoliv/
Luis Oliveira wrote:
Osicat should instruct CFFI/SB-ALIEN to load this library with :DONT-SAVE T to prevent saving a fixed path.
This a problem we're tackling in CFFI. For now, the best thing you can do is explicitly unload libosicat.so before saving the core, then reload it in an init hook.
That helped, thank you very much! Leslie -- http://www.linkedin.com/in/polzer
participants (2)
-
Leslie P. Polzer -
Luis Oliveira