Path: number1.nntp.dca.giganews.com!border1.nntp.dca.giganews.co   
   !nntp.giganews.com!newsfeed00.sul.t-online.de!t-online.de!newsfe   
   d.freenet.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail   
   From: ray    
   Newsgroups: alt.os.linux.ubuntu   
   Subject: Re: New Free Pascal Program not recognized   
   Date: Fri, 19 Jan 2007 15:42:21 -0700   
   Lines: 39   
   Message-ID:    
   References:      
   Mime-Version: 1.0   
   Content-Type: text/plain; charset=UTF-8   
   Content-Transfer-Encoding: 8bit   
   X-Trace: individual.net 0v8kdiyo+HObK5ZGf0kVRQGRjVSNXmXOK9WlBHbpvkDTx/41Qg   
   User-Agent: Pan/0.14.2.91 (As She Crawled Across the Table (Debian GNU/Linux))   
   Xref: number1.nntp.dca.giganews.com alt.os.linux.ubuntu:8467   
      
   On Fri, 19 Jan 2007 12:40:19 -0700, Tom Clydesdale wrote:   
      
   > On Fri, 19 Jan 2007 12:19:18 -0700, ray wrote:   
   >    
   >> On Thu, 18 Jan 2007 22:28:03 -0700, Tom Clydesdale wrote:   
   >>    
   >>> I just installed the Free Pascal Compiler via Synaptic which appears to   
   >>> run correctly and creates a supposedly executable file but which I   
   >>> cannot run.  I've checked permissions and it (the compiled program) will   
   >>> not run as either myself or via sudo.  Can anyone give me a clue as to a   
   >>> problem source or possible corrective path to go down?   
   >>>    
   >>> One thing that bothers me is the size of the executable file (>92k) for   
   >>> the very simple "Hello World" testing program!!!  When compiling there   
   >>> is no error indication with both an object and executable file created.   
   >>>    
   >>> I'm very new at this Linux arrangement and would greatly appreciate any   
   >>> thoughts.   
   >>    
   >> A couple of things spring to mind.   
   >>    
   >> 1) do an 'ls -s executable file' - the 'x' permission should be set. 2)   
   >> you may need to type './executablefile' in order to execute it. It is   
   >> customary not to have '.' in your path.   
   >    
   > That was the solution, many thanks, the compiler seems to have passed that   
   > test.   
   >    
   > Question: where can I find the logic regarding preceeding an executable   
   > file with "./"?   
      
   In order to run an executable when you type it's name, the system must be   
   able to find it. If you don't give the full name (absolute or relative,   
   like maybe /usr/bin/ls or testprogs/progname) then the system looks in   
   your 'path' which you can see by executing 'printenv'. Normally '.' which   
   is the current directory is not included in your path (I'm informed it's a   
   bad security practice) - "./filename" means "look for 'filename' in the   
   current directory".   
   --- Platinum Xpress/Win/WINServer v3.0pr5   
    * Origin: Omicron Theta BBS (1:261/20)