Stefano Iacus has been able to reproduce this on MacOS X (it was a
segfault in a later example), and we have just now committed a workaround.
I think it probably was an OS-specific quirk in vsnprintf.
On Tue, 8 Feb 2005, Prof Brian Ripley wrote:
Since no one else has this problem, I suggest you c
Hi Jake,
with this config
hal:~ jago$ gcc -v
Reading specs from /usr/libexec/gcc/darwin/ppc/3.3/specs
Thread model: posix
gcc version 3.3 20030304 (Apple Computer, Inc. build 1671)
hal:~ jago$ g77 -v
Reading specs from
/usr/local/lib/gcc/powerpc-apple-darwin6.8/3.4.2/specs
Configured with: ../gcc
Since no one else has this problem, I suggest you check the integrity of
your checkout, or, better, use an R-patched tarball that can easily be
verified. This looks very like a mismatched build and test: that is your
R build has not be updated to include the patch which is being tested.
A compl
Dear Developers,
I've been playing around with compiling R on my Debian Linux machine (dual
Athlon 1.4ghz) and my OS X machine (dual G5). I'm emailing now because
reg-tests-1.R fails during make check on my debian machine using gcc-3.4,
and on my OS X machine using gcc-3.3. I am using r-patched up