From: Craig L. <cla...@is...> - 2013-03-05 19:51:53
|
On Tue, 2013-03-05 at 21:28 +0200, Nikodemus Siivola wrote: > On 5 March 2013 19:16, Craig Lanning <cla...@is...> wrote: > > > I have put together a large application which uses foreign libraries. > > I made an executable using SAVE-LISP-AND-DIE. > > > > When it starts up I try to reload the foreign libraries, but it fails > > trying to load the first one. The call to LOAD-SHARED-OBJECT never > > returns. Instead it exits. > > Is there a backtrace or an error message? > > SAVE-LISP-AND-DIE assumes that shared objects can be loaded using same > pathnames as they had the first time. Maybe that's the issue. (Eg. if > you load using a relative pathname, and start the image later in a > different directory the same pathname is no longer valid.) The library pathnames will be different between the build host the execution host. The problem is that I was seeing this problem while I was still on the build host. The paths are still the same. Craig >>>CONFIDENTIALITY NOTICE>>> This electronic mail message, including any and/or all attachments, is for the sole use of the intended recipient(s), and may contain confidential and/or privileged information, pertaining to business conducted under the direction and supervision of the sending organization. All electronic mail messages, which may have been established as expressed views and/or opinions (stated either within the electronic mail message or any of its attachments), are left to the sole responsibility of that of the sender, and are not necessarily attributed to the sending organization. Unauthorized interception, review, use, disclosure or distribution of any such information contained within this electronic mail message and/or its attachment(s), is(are) strictly prohibited. If you are not the intended recipient, please contact the sender by replying to this electronic mail message, along with the destruction of all copies of the original electronic mail message (along with any attachments). |