On 27/03/2008, at 11:51 AM, Simon Urbanek wrote:
> 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 curren
t 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.
Bill Northcott
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
environment in which the R binary was
built. You can always go back to gcc-4.0 with 'sudo gcc_select 4.0'.
Bill Northcott
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
L_MAX_TEXTURE_SIZE, (GLint*) &maxSize);
but this generates warnings about signed and unsigned further down
scene.cpp. The resulting code works but it is clearly not right.
I can't find an email address for the maintainer and his web site
seems to be off the air just now.
Bill Northcott
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
copy of the makeinfo binary to save the
trouble of building it, please email me.
One final note: If you install the MinGW Msys-DTK rename the perl
binaries such as perl.exe which it provides. Otherwise they will be
used instead of the ActiveStat
the not too distant future gfortran will become part of the Xcode
packages.
Bill Northcott
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
