[R-sig-ME] Failure to load lme4 on Mac

[Simon Urbanek]

Daniel,

On Jul 16, 2010, at 6:05 PM, Daniel Myall wrote:

> Hi Simon,
> 
> The machine I'm primarily testing on has Mac OS X 10.6.4 with Xcode 3.2.2 (using gcc-4.2.1).

Yes, that setup works, but SL binaries are incompatible with Leopard so that doesn't help.


> The log from R CMD check is included below. I don't have any Leopard installs around anymore, although I am setting up a virtual machine with Mac OS X 10.5.8 and Xcode 3.1.4 to hopefully reproduce the bug.
> 

Can you tell me what are you using for that? I could use that myself :). I'm not aware of any VM so far that can run OS X 10.5.8 client as guest OS...


> If there is a bug in Mac OS X 10.5.8 or Xcode 3.1.4 resulting in the two errors in the tests that have so far been seen,  I am curious as to why it is only being exhibited with lme4. Once the VM has installed I'll play around with compile-time optimisations of lme4 to see if they are exposing the bug.
> 

It's not clear that the bug is on OS X or Xcode - it may or may not - from experience the issue is quite often a real bug but it can be masked other things such as memory layout, optimizations etc. I strongly suspect that in the current case since the result depends on the preceding code so it may be something like an uninitialized variable or so. We had both before, but lme4 is the only one failing in the current setup... 

Cheers,
Simon



> * using log directory '/Users/daniel/working/R-packages/lme4.Rcheck'
> * using R version 2.11.1 (2010-05-31)
> * using session charset: UTF-8
> * checking for file 'lme4/DESCRIPTION' ... OK
> * this is package 'lme4' version '0.999375-34'
> * checking package name space information ... OK
> * checking package dependencies ... OK
> * checking if this is a source package ... OK
> * checking for executable files ... OK
> * checking whether package 'lme4' can be installed ... OK
> * checking package directory ... OK
> * checking for portable file names ... OK
> * checking for sufficient/correct file permissions ... OK
> * checking DESCRIPTION meta-information ... OK
> * checking top-level files ... OK
> * checking index information ... OK
> * checking package subdirectories ... OK
> * checking R files for non-ASCII characters ... OK
> * checking R files for syntax errors ... OK
> * checking whether the package can be loaded ... OK
> * checking whether the package can be loaded with stated dependencies ... OK
> * checking whether the package can be unloaded cleanly ... OK
> * checking whether the name space can be loaded with stated dependencies ... OK
> * checking whether the name space can be unloaded cleanly ... OK
> * checking for unstated dependencies in R code ... OK
> * checking S3 generic/method consistency ... OK
> * checking replacement functions ... OK
> * checking foreign function calls ... OK
> * checking R code for possible problems ... OK
> * checking Rd files ... OK
> * checking Rd metadata ... OK
> * checking Rd cross-references ... OK
> * checking for missing documentation entries ... OK
> * checking for code/documentation mismatches ... OK
> * checking Rd \usage sections ... OK
> * checking Rd contents ... OK
> * checking data for non-ASCII characters ... OK
> * checking line endings in C/C++/Fortran sources/headers ... OK
> * checking line endings in Makefiles ... OK
> * checking for portable compilation flags in Makevars ... OK
> * checking for portable use of $BLAS_LIBS ... OK
> * checking examples ... OK
> * checking tests ... OK
> * checking package vignettes in 'inst/doc' ... OK
> * checking PDF version of manual ... OK
> 
> 
> 
> 
> On 17/07/10 12:48 AM, Simon Urbanek wrote:
>> The CRAN machine is Mac OS X 10.5.8 with Xcode 3.1.4 (using gcc-4.2) which is indeed the latest Xcode version for Leopard. If you have any hints as of why lme4 may be failing they are highly appreciated.
>> 
>> Thanks,
>> Simon
>> 
>>   
> 
>