hi !.

Steve Holden sholden at holdenweb.com
Fri Aug 25 15:09:53 EDT 2000


Piet van Oostrum wrote:
> 
> >>>>> wware at world.std.com (Will Ware) (WW) writes:
> 
> WW> Ravi C Venkatesan (rcv_dac at giaspn01.vsnl.net.in) wrote:
> >> Linux refuses to acknowledge the presence of the "configure" file, on
> >> typing "./configure". It replies "No such file, directory........"
> 
> WW> Sometimes the PATH variable is different for root than for a typical
> WW> user. Try logging into your non-root user account, and build python
> WW> that way. When it's built, log in as root and do "make install".
> 
> If you type ./configure the PATH is irrelevant.
> Check The #! line: it probably refers to a non-existent shell.
> --
> Piet van Oostrum <piet at cs.uu.nl>
> URL: http://www.cs.uu.nl/~piet [PGP]
> Private email: P.van.Oostrum at hccnet.nl

Does the configure script include carriage returns?  If so its
first line, usually something like

#!/usr/bin/sh

may be being misinterpreted.  I had trouble only this morning with
a Python script returning

bash: ./cgishell.cgi: No such file or directory.

After about ten minutes' headscratching I traced it to the file's being
in DOS format.  The carriage return at the end of the bang line

#!/usr/bin/python

was being interpreted as a part of the name of the executable, which
was consequently not being found.

Hope this helps.  To strip the returns, use something like

	tr -d "\015" < oldprogram.py > newprogram.py

regards
 Steve
-- 
Helping people meet their information needs with training and technology.
703 967 0887      sholden at bellatlantic.net      http://www.holdenweb.com/



More information about the Python-list mailing list