Skip to content

issue with compiling r6

3 messages · Peter Dalgaard, Ben Bolker

#
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

  I am painfully aware that this is most likely a problem with my
system, but I am nevertheless going to ask if anyone has any
ideas/suggestions for diagnosis and trouble-shooting.

- From a clean checkout of release 66624 on Ubuntu 12.04 (32-bit, sorry!):
gcc (Ubuntu/Linaro 4.6.4-1ubuntu1~12.04) 4.6.4

svn checkout https://svn.r-project.org/R/trunk/
tools/rsync-recommended

cd ../r-build
../r-devel/configure

R is now configured for i686-pc-linux-gnu

  Source directory:          ../r-devel
  Installation directory:    /usr/local

  C compiler:                gcc -std=gnu99  -g -O2
  Fortran 77 compiler:       gfortran  -g -O2

  C++ compiler:              g++  -g -O2
  C++ 11 compiler:           g++  -std=c++0x -g -O2
  Fortran 90/95 compiler:    gfortran -g -O2
  Obj-C compiler:	

  Interfaces supported:      X11, tcltk
  External libraries:        readline, lzma
  Additional capabilities:   PNG, JPEG, TIFF, NLS, cairo
  Options enabled:           shared BLAS, R profiling

  Capabilities skipped:      ICU
  Options not enabled:       memory profiling

make fails at:

byte-compiling 'methods'
initializing class and method definitions ...Error: .onLoad failed in
loadNamespace() for 'methods', details:
  call: new("classRepresentation")
  error: could not find function "isVirtualClass"

The only other oddity of my system/potential clue is that symbolic
links sometimes behave strangely because I am working on a VirtualBox
virtual machine with a virtual Linux filesystem layered over an HGFS
filesystem.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJUGaMGAAoJEOCV5YRblxUHEvcIAKpNQbCRXhcOB5BhYKd5lnvZ
VLVfRQhM7rYDt9f9XFGwNigFAvA/47L9u0PDcYYVMJHLFUWObqMcsi4qfKA5y0LB
K8ZVG766HZqsLLFZVx7wzP1Ict0IcO1JudtkTSCfXXIq00lj6Dhs+6vU4HWoN6vg
rXQokhHX1cedNRKCLlXwHblN0DHZsj1EXTUSDzYJA3p1sO7KUqXmzE76+62vANKj
tLvBXk7771szHDmnD3oosLaYM0c7pEUzMJIgIg3TP+CBMVsMcrPMgVJ7zvMiWwQd
/2Qji9HBLkD6ODa29JYvn1DTXZzigF/gnG7ZBx8xN8d7rQ8v/cKY2ZNk8fg+4II=
=m0Kr
-----END PGP SIGNATURE-----
#
On 17 Sep 2014, at 17:04 , Ben Bolker <bbolker at gmail.com> wrote:

            
Others have been seeing this since r66622, so I think you're just suffering the "unsuffered consequences" (unsuffered by regular users, that is; people who run development versions will suffer occasionally). Just hang on for a while.
That's _revision_ 66624, please. It is only "released" in the sense that it isn't kept secret. 

-pd

  
    
#
Thanks for the information.  It's the old story -- it's only once you
finally convince yourself that the problems are always on your end and
never bugs in the other guy's (development) code that you actually
encounter bugs in the other guy's code.

  Ben Bolker
On 14-09-17 11:32 AM, peter dalgaard wrote: