ralna / SIFDecode

A package to decode SIF optimization test examples for use by CUTEst and GALAHAD
Other
8 stars 3 forks source link

SIFDecode test expects sifdecoder in PATH #10

Open jfowkes opened 8 months ago

jfowkes commented 8 months ago

As found by @Letizia97 Running the SIFDecode test post installation fails unless sifdecoder is in the PATH:

$ cd $SIFDECODE/src ; make -f $SIFDECODE/makefiles/$MYARCH test

( cd decode ; make -f /home/vol04/scarf964/cutest/sifdecode/makefiles/pc64.lnx.gfo \
                     test PWD=/home/vol04/scarf964/cutest/sifdecode/src/decode )
make[1]: Entering directory `/home/vol04/scarf964/cutest/sifdecode/src/decode'
echo ""

echo " Decode unconstrained SIF file"
 Decode unconstrained SIF file
cd /home/vol04/scarf964/cutest/sifdecode/sif/ ; sifdecoder -A pc64.lnx.gfo ALLINITU
/bin/sh: sifdecoder: command not found

Surely the test should be using $SIFDECODE/bin/sifdecoder?

nimgould commented 8 months ago

This is true, but of course a user is told to do this at the end of the install, viz

You should now add the following to your .bashrc file: ... export PATH="${SIFDECODE}/bin:${PATH} ...

But yes, it certainly doen't hurt to add this entire path. I will add

jfowkes commented 8 months ago

Oh are they? I haven't been doing that for years...

nimgould commented 8 months ago

I guess your Mac is so smart that it finds executables using AI :)

The message occurs at the end of the install (and says other things about man pages, etc)

If you don't do this, you won't be able to use sifdecoder standalone

jfowkes commented 8 months ago

Haha if only, I think I've just never needed to use standalone sifdecoder.