Error - template LAYOUT-DATA-WRAPPER not found

A configuration error was detected in the CGI script; the LAYOUT-DATA-WRAPPER template could not be found.

Error - template STYLE-SHEET not found

A configuration error was detected in the CGI script; the STYLE-SHEET template could not be found.

Error - template SUB-TOP-BANNER not found

A configuration error was detected in the CGI script; the SUB-TOP-BANNER template could not be found.
Subject:
From:
Dave Gillett <[log in to unmask]>
Reply To:
PCSOFT - Personal Computer software discussion list <[log in to unmask]>
Date:
Wed, 19 Jul 2000 01:42:33 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (41 lines)
On 18 Jul 00, at 15:04, Stephen Bourgeois wrote:

> I compiled my first program in C++ in Redhat Linux 6.1. I copied
> everything verbatim from the intro books. I compiled the program as
> directed ( g++ firstprog.cxx -o firstprog ). The correct executible
> file was created and visible in the directory ( firstprog ). But
> when I went to execute it, I got the error message "Command not
> found " from BASH stating the command and was not  available. I
> opened the executible file with VI to make sure it was available to
> other programs, which it was. But I kept getting the same error
> message when I tried to execute it as if it was not there.
>
> I changed it from executible ( chmod -x firstprog) and back again
> ( chmod +x firstprog). Still the same error message.
>
> Any suggestons ?

  I'm no UNIX guru, but I've encountered a similar condition, and a
rather simple workaround which is likely to also apply to your case.

  My *speculation* is that when you type "firstprog", the shell
(bash, in your case) pulls up the environment variable that specifies
common execution paths, and looks in each path in turn for an
executable by that name -- and doesn't find one.
  The workaround is to type "./firstprog"; since this specifies "in
the current directory", the shell is not allowed to go looking in the
various path folders.  It looks only where it has been told, and
succeeds.

  This suggests that a longer-term fix might be to modify the user
profile to include "." in the execution path -- but I'm fairly
certain there is some reason why this is not the default profile
setting.  That's getting beyond what I've needed to know for the
little bit of UNIX I use.

David G

             Do you want to signoff PCSOFT or just change to
                    Digest mode - visit our web site:
                    http://nospin.com/pc/pcsoft.html

ATOM RSS1 RSS2

LISTSERV.ICORS.ORG Secured by F-Secure Anti-Virus CataList Email List Search Powered by LISTSERV