Skip to content

Error compiling R on RS6000 (PR#475)

5 messages · pgutwin@us.ibm.com, Friedrich Leisch, Peter Dalgaard +2 more

Original
pgutwin@us.ibm.com
# 
Full_Name: Paul Gutwin
Version: R-1.0.0
OS: AIX 4.2.1
Submission from: (NULL) (198.133.22.67)


R-1.0.0 fails to compile. I'm using the config.cache file from a successful
compliation of R-0.65.0 (prob #290, fixed thanks to Thomas Vogels @ CMU). 
Compiling R-1.0.0 fails with the following error messages:

make
Target "R" is up to date.
	gcc -I. -I../include -I../../src/include -I../../src/include/R_ext 
-DHAVE_CONFIG_H -mno-fp-in-toc -g -O2 -c Rsock.c -o Rsock.o
In file included from Rsock.c:34:
/usr/include/unistd.h:162: parse error before `lseek64'
/usr/include/unistd.h:162: parse error before `off64_t'
/usr/include/unistd.h:162: warning: data definition has no type or storage
class
In file included from /usr/include/sys/lockf.h:41,
                 from /usr/include/unistd.h:382,
                 from Rsock.c:34:
/usr/include/sys/stat.h:127: parse error before `soff_t'
/usr/include/sys/stat.h:127: warning: no semicolon at end of struct or union
/usr/include/sys/stat.h:146: parse error before `st_size'
/usr/include/sys/stat.h:146: warning: data definition has no type or storage
class
In file included from /usr/include/unistd.h:382,
                 from Rsock.c:34:
/usr/include/sys/lockf.h:60: parse error before `off64_t'
In file included from Rsock.c:34:
/usr/include/unistd.h:417: parse error before `off64_t'
/usr/include/unistd.h:438: parse error before `off64_t'
/usr/include/unistd.h:440: parse error before `ualarm'
/usr/include/unistd.h:440: warning: parameter names (without types) in function
declaration
/usr/include/unistd.h:440: warning: data definition has no type or storage
class
/usr/include/unistd.h:441: warning: parameter names (without types) in function
declaration
/usr/include/unistd.h:474: parse error before `fclear64'
/usr/include/unistd.h:474: parse error before `off64_t'
/usr/include/unistd.h:474: warning: data definition has no type or storage
class
/usr/include/unistd.h:475: parse error before `off64_t'
make: 1254-004 The error code from the last command is 1.


Stop.
make: 1254-004 The error code from the last command is 2.


Stop.
make: 1254-004 The error code from the last command is 1.


Stop.
make: 1254-004 The error code from the last command is 1.


Stop.

Compilation exited abnormally with code 2 at Tue Mar  7 10:15:58


-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !)  To: r-devel-request@stat.math.ethz.ch
_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._
Friedrich Leisch
# 
p> Full_Name: Paul Gutwin
p> Version: R-1.0.0
p> OS: AIX 4.2.1
p> Submission from: (NULL) (198.133.22.67)


p> R-1.0.0 fails to compile. I'm using the config.cache file from a successful
p> compliation of R-0.65.0 

Uhm, why would you want to do that???

Have you tried building from a clean (fresh) source tree?

.f
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !)  To: r-devel-request@stat.math.ethz.ch
_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._
Peter Dalgaard
# 
pgutwin@us.ibm.com writes:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^

What on earth gives you the idea that that might work?? The configure
scripts have changed many a time since 0.65.0. Or was config.cache a
typo?
Thomas J Vogels
# 
Hi,

  I'll assume Paul meant config.site which contains all the extra
  compiler and linker flags and those flags are somewhat involved in
  his environment.  Triggered by Paul's email I tried to
  compile R-1.0.0.  It compiles cleanly but dies with "Illegal
  Instruction" upon start.  Sorry, I don't have any further insight
  into this problem at this time.

  I've been working on my Linux box instead of the my AIX workstation
  lately, so I didn't see this earlier.  Actually I've been so busy
  using R, that I've missed to congratulate on the release or 1.0.
  Thanks to all who work on R which has been a tremendous help for me!

  -tom


Peter Dalgaard BSA <p.dalgaard@biostat.ku.dk> writes:

  
    

      
      
    

  


  


      

    

    

      
      

        


  

        

      Douglas Bates
    

    

      
      #
    

  


  

      
Thomas J Vogels <tov@ece.cmu.edu> writes:

            

      
      
      
    

        
Do the compilers need special flags to control IEEE floating point
behavior?  One of the first things that R does on startup is to force
an evaluation of 1.0/0.0 and store the result as a global "Infinity".
On some architecture/compiler combinations this will generate an error
unless you instruct the compiler to insert special code for full IEEE
compliance.
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-devel mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !)  To: r-devel-request@stat.math.ethz.ch
_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._