From lai at lindaspaces.com  Thu Sep  1 00:01:47 2005
From: lai at lindaspaces.com (Jennifer Lai)
Date: Wed, 31 Aug 2005 18:01:47 -0400
Subject: [Rd] Build Portland Group Compiler
In-Reply-To: <43162853.6070902@lindaspaces.com>
References: <43162119.1010503@lindaspaces.com>
	<x2oe7d4vux.fsf@turmalin.kubism.ku.dk>
	<43162853.6070902@lindaspaces.com>
Message-ID: <431628CB.7080900@lindaspaces.com>

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 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?
>
> Regards,
> Jennifer
>
> Peter Dalgaard wrote:
>
>> Jennifer Lai <lai at lindaspaces.com> 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 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.
>>
>>  
>>
>
>



[Rd] Build Portland Group Compiler
Jennifer Lai