From: Bakul Shah bakul@bitblocks.com
To: Marc Feeley feeley@iro.umontreal.ca Cc: Steve Graham jsgrahamus@yahoo.com; Gambit List Gambit-list@iro.umontreal.ca Sent: Tuesday, March 19, 2013 12:43 PM Subject: Re: [gambit-list] Running gambit program
-rwxrwxrwx 1 root root 45 Feb 20 13:20 /usr/bin/gsi
Notice the filesize. I bet this was a shell script that didn't pass arguments to the real gsi (or may be this gsi was doing something completely different). If this file is still around Steve can `cat -v' it to see what's in it. cat -v just in case it contains some binary data.
-rwxr-xr-x 1 root root 5320182 Mar 19 11:05 /usr/src/gambit/gsi/gsi
Notice the different modify date of each gsi. My guess is /usr/bin/gsi was locally created and left over from something earlier. [And there is an admin bug: -rwxrwxrwx implies root is likely using a umask of 0! Root should use `umask 022']
I would like to understand what went wrong. Previously you said that you bui lt Gambit in a conventional way:
...
However, you later said that gsi was in /usr/bin/gsi . This is very strange because building Gambit conventionally will install gsi in /usr/local/Gambit- C/bin/gsi , so how come it ended up in /usr/bin/gsi? And why did it not run properly? I know you fixed your problem, but it would be worthwhile spending some time to understand what the problem is so that I can fix the makefiles if they are at fault, for the benefit of others.
The one in /usr/bin was a bash file which changed the directory to /usr/local/gambit/gsi and executed ./gsi
Maybe some of this came from Mint Linux' package manager.
Steve