My silly mistake. I didn't get the error message the second time is
because I have set LD_LIBRARY_PATH. If this value is unset, I would
have gotten the same error message,
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot
Jennifer Lai <[EMAIL PROTECTED]> writes:
> I can't duplicate the error message. After running "configure
> --host=x86_64-unknow-linux-gnu" for the first time, I was able to run
> configure without providing --host argument. Even start with a fresh
> copy of R-devel didn't help me to get the origin
Forgot to mention, here are #define long and int value in config.log
from second configure run (without --host argument)
| #define SIZEOF_INT 4
| #define INT_32_BITS 1
| #define SIZEOF_LONG 8
| #define SIZEOF_LONG_LONG 8
| #define SIZEOF_LONG_DOUBLE 16
Regards,
Jennifer
Jennifer Lai wrote:
> I
I can't duplicate the error message. After running "configure
--host=x86_64-unknow-linux-gnu" for the first time, I was able to run
configure without providing --host argument. Even start with a fresh
copy of R-devel didn't help me to get the original error. Is the host
info been cached somewhe
Jennifer Lai <[EMAIL PROTECTED]> writes:
> Hi,
> I built R with Portland Group compiler, but I noticed one thing that
> when I ran configure for the first time on AMD machine, I got the
> following error:
>
>
> checking whether the C compiler works... configure: error: cannot run C
> comp
