Sending this to oscar-devel would certainly have made much more sense. As far as /opt/oscar being hard coded, in this case I was installing from /opt/oscar anyway so that should not have broken anything, I don't think. Anyway, thought I would throw this out for the record, I wasn't sure if anyone had tried to get this to work with 5.0 on RHEL4.
On 7/19/06, Bernard Li <[EMAIL PROTECTED]> wrote: > Hi Mike: > > > Processing /var/lib/oscar/packages/mpiBLAST/config.xml for > > package mpiBLAST ... > > Writing a new Packages record for package mpiBLAST > > --> About to run > > /var/lib/oscar/packages/mpiBLAST/scripts/setup for mpiBLAST > > /var/lib/oscar/packages/mpiBLAST/scripts/setup: line 8: > > /opt/oscar/scripts/generic-setup: No such file or directory > > Script /var/lib/oscar/packages/mpiBLAST/scripts/setup exitted badly > > with exit code '127' at OpderDownloadPackage.pm line 433 > > Failed to run setup script for mpiBLAST at > > /usr/lib/perl5/site_perl/Qt.pm line 449 > > It's possible that instead of $OSCAR_HOME/scripts/generic-setup, > "/opt/oscar" was hardcoded. > > BTW, this should really go to oscar-devel, and cc: Doug, the author of > the package. > > Thanks, > > Bernard > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
