das wrote: > On Thu, 2007-10-11 at 13:28 -0400, Mauriat M wrote: >> - Try compiling as non-root (only the 'make install' requires root >> access) > > I cannot even run ./configure, neither as root, nor as user. Result is > 'Permission denied'. > > Both root/user can run it as: sh ./configure What are the permissions on ./configure, I'm betting it doesn't include "x". You can't execute with out "x". You *can* however, read it as input to the shell if it has "r" permissions. > In both the cases the output is identical. I am quoting the whole thing: > > << > sh ./configure > checking build system type... i686-pc-linux-gnu > checking host system type... i686-pc-linux-gnu > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for gawk... gawk > checking whether make sets $(MAKE)... yes > checking whether to enable maintainer-specific portions of Makefiles... > no > checking for style of include used by make... GNU > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... configure: error: cannot run C > compiled programs. Something is squashing your execute permissions. > If you meant to cross compile, use `--host'. > See `config.log' for more details. > > > The config.log also giving something like this: > > << > /usr/bin/uname -p = unknown > /bin/uname -X = unknown > > /bin/arch = i686 > /usr/bin/arch -k = unknown > /usr/convex/getsysinfo = unknown > hostinfo = unknown > /bin/machine = unknown > /usr/bin/oslevel = unknown > /bin/universe = unknown > > > This first line, /usr/bin/uname is actually /bin/uname > > Is this the source of all trouble? Some non-standard file placing in F7, > or something in gcc has got corrupted? > > Thank you for trying to help. > > -- > das > -- Kevin J. Cummings kjchome@xxxxxxx cummings@xxxxxxxxxxxxxxxxxx cummings@xxxxxxxxxxxxxxxxxxxxxxx Registered Linux User #1232 (http://counter.li.org)
