Thank you Bhaskar for the testing details! The will definetely be useful to provide at least a minimal test of having things built/installed correctly. My family keeps me heavily occupied this weekend so I will have a chance to look at it with a clear head only early next week. But regarding:
> $ $gtm_dist/mumps -direct > GTM>write $text(^%RSEL) ; Notice the blank line > GTM>zhelp ; This will clear the screen and generate an error > (clears the screen) > Error in GT.M help utility > GTM>halt > $ > So you definitely need a postinstall script, and you cannot just > install it in one place and move it. I still hope that we could find the relevant code where the filename gets embedded so we could either patch it simply to look for the original .m in the same directory where the .o/.so is, or just to provide compile time argument (e.g. via env variable) to allow "install" into a location with a predefined prefix (i.e. temporary build top directory) which would not be placed into the generated .o file, thus allowing to install the binary into the location without that prefix. Any hints would be more than welcome where to dig in the right direction ;-) -- Yaroslav O. Halchenko Postdoctoral Fellow, Department of Psychological and Brain Sciences Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
