I found a workaround,that is, to disable attribute caching using the
"noac" nfs option.
#These two worked on tiger 10.4.3
exec -c "console=ttyAM0,115200
ip=10.0.2.155:10.0.2.150:10.0.2.1:255.255.255.0:ts7250
nfsroot=10.0.2.150:/Data/nfsroot,noac"
#fstab entry they have to match
10.0.2.150:
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 fil
cat > foo.cpp
int main(){return 0;}
c++ foo.cpp
ll a.out
-rwxr-xr-x 1 root tsarm 12124 Nov 15 15:54 a.out
./a.out
but if I
gcc foo.cpp
ll a.out
-rw-r--r-- 1 root tsarm 12060 Nov 15 15:55 a.out
but if I do it again
# gcc foo.cpp
ll a.out
-rwxr-xr-x 1 root tsarm 12060 Nov 15 15:58 a.out
On
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 `--hos
I am trying to build python2.4.2 on an arm 9 running Debian 3 Sarge
when I run ./configure it fails with
./configure
checking MACHDEP... linux2
checking EXTRAPLATDIR...
checking for --without-gcc... no
checking for --with-cxx=... no
checking for c++... c++
checking for C++ compiler default output
