Comment 59 for bug 88570

hi Rafal

Thanks for posting your config.log file :)

From what I can see your running a slightly different kernel ('2.6.22-ck1') from the normal stock kernel '2.6.20-16-generic' (at the time of this writing), and this may have an impact, although I can't be sure of that :)

oh and extra parameters seem to be attached when the configure script checks the default output name of the c compiler on your system.

Your config.log contains the following line: -

configure:2367: checking for C compiler default output file name
configure:2394: gcc -O2 -mtune=k8 -funroll-loops -ffast-math -fomit-frame-pointer -fno-exceptions" conftest.c >&5
cc1: error: unrecognized command line option "-fno-exceptions""
configure:2397: $? = 1

(incidentally i thing gcc is objecting to the " character at the end of the -fno-exception parameter and not -fno-exceptions parameter itself)

whereas my config.log file contains: -

configure:2367: checking for C compiler default output file name
configure:2394: gcc conftest.c >&5
configure:2397: $? = 0

I'm mainly a windows developer, so I'm a little out of my depth in the linux world but I think your answer might lie in those parameters?

Regards

John.