[comp.windows.interviews] Installation Report 3.0-beta

ege@scs.fiu.edu (Raimund K. Ege) (04/27/91)

we compiled InterViews 3.0-beta without any hitch
on Sun 4s running SunOS 4.1.1 and the Sun C++ compiler.

During installation we encountered a minor problem for the script files:

+ install -c -m 0755 cpu ../../.././installed/bin/SUN4
cp: 0755: No such file or directory
chmod: ../../.././installed/bin/SUN4/0755: No such file or directory
+ install -c -m 0755 ibmkmf ../../.././installed/bin/SUN4
cp: 0755: No such file or directory
chmod: ../../.././installed/bin/SUN4/0755: No such file or directory
+ install -c -m 0755 ivmkmf ../../.././installed/bin/SUN4
cp: 0755: No such file or directory
chmod: ../../.././installed/bin/SUN4/0755: No such file or directory
+ install -c -m 0755 remind ../../.././installed/bin/SUN4
cp: 0755: No such file or directory
chmod: ../../.././installed/bin/SUN4/0755: No such file or directory

After installation we found that all InterViews applications ran,
except for ifb, which reports a segmentation fault on startup.
At first we did not notice the white on black problem for Sun
monochrome displays, since we had used color displays and X terminals
(NCD and GraphOn). Fix1 as posted in this news group fixed that problem.

Raimund K. Ege                             School of Computer Science
                                             Florida Int'l University
ege@scs.fiu.edu           (305) 348-3381              University Park
ege@servax.bitnet     FAX (305) 348-3549              Miami, FL 33199

interran@lurch.Stanford.EDU (John Interrante) (04/28/91)

In article <3429@kluge.fiu.edu> ege@scs.fiu.edu (Raimund K. Ege) writes:

   During installation we encountered a minor problem for the script files:

   + install -c -m 0755 cpu ../../.././installed/bin/SUN4
   cp: 0755: No such file or directory
   chmod: ../../.././installed/bin/SUN4/0755: No such file or directory

I never saw this problem before, but I can guess what happened.  It
was a combination of three mistakes, two ours and one yours:

 1) We had an executable script called `install' in src/bin/scripts.
 2) You had `.' ahead of /usr/bin in your PATH.
 3) The script had a bug in it.

We should never have had an executable script called install in
src/bin/scripts, but we weren't careful enough when we made the
3.0-beta snapshot.  When you tried to install the script files, make
invoked src/bin/scripts/install instead of /usr/bin/install because
you had `.' ahead of /usr/bin in your PATH.  The script was very old
(it came from X11R3), so it had a bug which caused the error messages
you saw.

You should delete src/bin/scripts/install and you should put `.' last
in your PATH to make sure you don't accidentally invoke an executable
file in the current directory again because it has the same name as a
command.
--
John Interrante / interran@lurch.stanford.edu