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 run C compiled programs. If you meant to cross compile, use `--host'. Thank you for the help! Sincerely, Jennifer Peter Dalgaard wrote: >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 original error. Is the host >>info been cached somewhere in R? >> >> > >Not that I know of... Back in the old days we had config.cache playing >tricks on people, but it shouldn't be there anymore. > >If you're not already doing so, do yourself a favour and build in a >separate directory, keeping the sources untouched. It's much easier to >clean up and start over that way. > > > >>>>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 compiled programs. >>>>If you meant to cross compile, use `--host'. >>>>See `config.log' for more details. >>>> >>>> >>>> >>>>so I tried to set host=x86_64-unknown-linux-gnu, which seems to >>>>work, except what puzzles me is that there is warning messages >>>>indicating C longs are 4 bytes. >>>> >>>>******************************************* >>>>% configure --host=x86_64-unknown-linux-gnu >>>>. >>>>. >>>>. >>>>R is now configured for x86_64-unknown-linux-gnu >>>> >>>> Source directory: . >>>> Installation directory: /usr/local/R.pgcc >>>> >>>> C compiler: /usr/pgi/linux86-64/6.0/bin/pgcc -g >>>>-O2 -mieee-fp >>>> C++ compiler: /usr/pgi/linux86-64/6.0/bin/pgCC -g >>>> Fortran compiler: /usr/pgi/linux86-64/6.0/bin/pgf77 -O2 >>>> >>>> Interfaces supported: X11 >>>> External libraries: readline >>>> Additional capabilities: PNG, JPEG, MBCS, NLS >>>> Options enabled: R profiling >>>> >>>> Recommended packages: yes >>>> >>>>configure: WARNING: assuming C ints are 4 byte on x86_64-unknown-linux-gnu >>>>configure: WARNING: assuming C longs are 4 byte on x86_64-unknown-linux-gnu >>>>configure: WARNING: you cannot build info or html versions of the R manuals >>>> >>>> >>>>Am I defining a wrong host? >>>> >>>> >>>> >>>You're not doing yourself a favour, anyway. 4-byte longs are >>>definitely not a good idea on Linux. What is worse, you are building a >>>cross-target, which means that configure is not even going to try >>>running any compiled programs, not that they work any better than >>>before. >>> >>>The thing to do is to look inside config.log and see what causes >>>configure to conclude that you cannot run C compiled programs. >>> >>> >>> >>> >> >> >> > > > ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
