Configure failing why?

Samuel M. Smith smithsm at
Fri Nov 18 01:58:40 CET 2005

Thanks for your help.
Your confirmation that gcc should be setting the execute permissions  
gave me something easy
to test against.

I finally discovered the problem. It was nfs.  The file system was  
nfs mounted and nfs is causing
the aberrant behavior. If I did the test on the onboard flash file  
system it worked. I finally used a different
nfs server and the problem went away.

I was serving nfs from a Mac OS X 10.4.3 machine. The problem did not  
occur on OS X 10.4.2 not does it occur
when serving nfs from OS X 10.3.9
It something new introduced in 10.4.3. I don't have a fix for it.
Anyone have a suggestion it would help.

On 15 Nov, 2005, at 15:40, Fredrik Lundh wrote:

> Samuel M. Smith wrote:
>> I am trying to build python2.4.2 on an arm 9 running Debian 3 Sarge
>> configure:1842: ./a.out
>> ./configure: line 1: ./a.out: Permission denied
>> configure:1845: $? = 126
>> configure:1854: error: cannot run C++ compiled programs.
>> If you meant to cross compile, use `--host'.
>> See `config.log' for more details.
>> It appears that for some reason the a.out file that the configure
>> script is making is not getting execute permissions enable by the
>> configure script
> on a sane standard Unixoid system, the compiler is required to set the
> following permission flags
> if and only if the program was successfully compiled and linked.
> what happens if you do
>     $ cat >foo.cpp
>     int main(){ return 0; } <control-D>
>     $ c++ foo.cpp
>     $ ls -l a.out
> ?
> </F>
> -- 

Samuel M. Smith Ph.D.
2966 Fort Hill Road
Eagle Mountain, Utah 84043
801-768-2768 voice
801-768-2769 fax
"The greatest source of failure and unhappiness in the world is
giving up what we want most for what we want at the moment"

More information about the Python-list mailing list