Well, I got the rpm file built. If you put this in the beginning of the rpm .spec file:
%define __spec_install_post $rpmlib/brp-compress || : the rpm processor doesn't do the strip steps, and the resulting executable seems fine (it is now the same size as the one produced from the 'unicon mcdu.icn' at the command line. However, after the rpm install, the file is in the correct location, which is in the path, but doesn't run without a full path name: > mcdu error in startup code mcdu: cannot open interpreter file But, if given the full pathname to the executable, it runs fine: > /usr/local/efr/bin/mcdu <program starts up...> Does the executable need a 'patchstr' run against it? Do I need an IPATH or LPATH set? Does the executable depend on the startup file's full pathname to find its own executable? Wendell Turner ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ Unicon-group mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unicon-group
