On Thu, 23 Sep 2004 10:15:40 -0700
Steven Pasternak
Jerry Feldman wrote:
On Thu, 23 Sep 2004 09:20:40 -0700 Steven Pasternak
wrote: compiled programs. If you meant to cross compile, use `--host'. See `config.log' for more details. steven@linux:~/Documents/other/RPMs/SuSE/Look/kerastik-0.1>
I use SuSE 9.1 kernel 2.6.4-52-default with gcc-3.3.3 (the one that came with SuSE.) I'm pretty sure that it is the compiler because i did> 'export CC=~/bin/gcc' which was an empty text file, and got the same
output except the line:
checking for gcc... gcc
was replaced with:
checking for gcc... /home/steven/bin/cc
and i got the same
checking whether the C compiler works... configure: error: cannot run>C compiled programs. If you meant to cross compile, use `--host'. See `config.log' for more details.
stuff. what is wrong?
export CC=~/bin/gcc Do NOT do this. You are pointing to gcc in your HOME directory (eg /home/steven/bin).
Here is a test you should run: 1. Build a simple hello world: #include
int main() { printf("Hello, world!\n"); return 0; } 2. compile that program: gcc hello.c -o hello 3. run the program: ./hello
This will test that the C compiler works, and that your include files are installed.
That worked, but doing './configure' still gives me the crud, and 'sh ./configure' still gives me trouble. Make sure that the export statement is not in your ./bashrc Remember that a script is going to read your environment because it is a new process. So, if you simply unset it in the current environment and did not fix your .bashrc, then the problem would recur.
After cleaning up your environment try the ./configure.
The first line of configure is usually:
#! /bin/sh
That means it will execute /bin/sh, or the Bourne shell.
It appears to me that you put stuff in your .bashrc that is causing
problems, or for some reason the symlink in /bin got clobbered.
lrwxrwxrwx 1 root root 4 2004-01-26 12:14 /bin/sh -> bash
On EVERY Unix or Linux site you must have the Bourne shell in /bin.
Since the ./configure script should have #! /bin/sh it might appear that
it is clobbered or that your environment is doing something wierd.
Try this, and you should get a result similar to mine.
gaf@gaf:~> /bin/sh
sh-2.05b$
--
Jerry Feldman