[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference cookie::archive_backup

Title:	Archive/Backup

Moderator:	COOKIE::MHUAIG

Created:	Wed Sep 08 1993
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	479
Total number of notes:	2283

410.0. "Solaris installation problems" by CX3PST::BSS::SAUL () Wed Mar 26 1997 14:09

Hi,

Customer is having problems with a Solaris installation.  When he puts in the
configure command he gets...

GNU C file not found

and then all kinds of garbage.  I'm having the customer send a log file of the
output.  But for now I was wondering if there is a way to set verbose (verify) on
the configure command.  Any gotchas with the Solaris boxes?  Also, how tight are
the supported versions.  What I mean is, its documented that we support 2.5 but how
about 2.5-1.  Thanks.

Ted

T.R Title User Personal
Name Date Lines

410.1 some general info COOKIE::LEWIS Fri Mar 28 1997 08:30 36

T.R	Title	User	Personal Name	Date	Lines
410.1	some general info	COOKIE::LEWIS		`Fri Mar 28 1997 08:30`	36
	Hi Ted, We have not tried the installation on anything but 2.5, because that is all we have at this point. We are trying to get some more versions of all of the various platforms so we can try it and "qualify" on them. I would suspect it will work on 2.5-1, but we have not had a chance to actually try it. Looking at the log file is probably our best bet. Another thing to have them check is their "path" The path environment variable indicates where and in what order the operating system looks for executable files. Have them set their default to the directory from which they were doing the configure (the directory should be tar-1.11.8 if they are building gtar) and then do which configure it should tell you ./configure (current directory) also do printenv PATH (note uppercase) and let us see that. Also see if he can just compile any program, using cc or gcc, and have him do a which cc and which gcc The "which" command tells us what exe it will execute when the command is executed. For example on my system I see seymor> which cc /usr/ucb/cc seymor> which gcc /usr/local/bin/gcc Thanks Jim

Hi Ted,

We have not tried the installation on anything but 2.5, because that is all
we have at this point.  We are trying to get some more versions of all of the
various platforms so we can try it and "qualify" on them.  I would suspect it
will work on 2.5-1, but we have not had a chance to actually try it.  Looking
at the log file is probably our best bet.  

Another thing to have them check is their "path"  The path environment variable
indicates where and in what order the operating system looks for executable
files.

Have them set their default to the directory from which they were doing the
configure (the directory should be tar-1.11.8 if they are building gtar) 
and then do
which configure
  it should tell you ./configure (current directory)

also do printenv PATH    (note uppercase)
and let us see that.
       
Also see if he can just compile any program, using cc or gcc, and have him
do a
  which cc   and which gcc

The "which" command tells us what exe it will execute when the command is 
executed.  For example on my system I see

seymor> which cc
/usr/ucb/cc
seymor> which gcc
/usr/local/bin/gcc


Thanks
Jim