On Mar 26, 2008, at 8:05 PM, Bill Northcott wrote: > On 26/03/2008, at 10:00 PM, Georgios wrote: >> I have installed gcc 4.2 and gfortran 4.2 from the available sources >> on the >> web page and am using the copy and paste guide on the page. >> >> Now everything seems to be going fine until the point where the R >> packages >> are tested. In particular when the regression tests are run I get the >> following. >> >> running regression tests >> running code in 'reg-tests-1.R' ...\c >> OK >> running code in 'reg-tests-2.R' ...\c >> OK >> comparing 'reg-tests-2.Rout' to './reg-tests-2.Rout.save' ...\c >> 3756c3756 >> < The decimal point is 1 digit(s) to the right of the | >> --- >>> The decimal point is at the | >> 3762c3762 > > It may or may not be relevant, but there is a catastrophic bug in > log10() in 10.5.2 for x86_64: it returns 0 for all arguments. This > has been discussed on the Scitech list. Apple think they have fixed > it, but I am sure they would want to hear of other cases or possible > compiler issues, if it is their compiler you are using. > > So if you can get a minimal test case it would be very good to submit > a bug. It may be worth doing even if you cannot get a minimal case > because all the sources are readily available. > > Finally last time I looked a few days back Simon's 64 bit Intel builds > were failing. >
Yes, the gcc-4.2 is known to be broken for x86_64 as you describe above (or in fact it miscompiles a few other things, too). Interestingly llvm-gcc-4.2 suffers from the same problem. That is the reason why the 64-bit binaries are currently not offered. Switching to gcc-4.0 breaks other things on other targets, so there is no universal (and maintainable) solution that I'm aware of. Thanks, Simon ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
