I can consistently get a segfault from Mavericks 3.1 and I suspect it
is from a mismatch
of compiled code. Can this type of mismatch be detected when the
package is loaded?
When I moved to the Mavericks R distribution, I copied packages from
my 3.0 (SnowLeopard) library and then did an
- Original Message -
From: Richard M. Heiberger r...@temple.edu
To: r-sig-mac@r-project.org
Sent: Thursday, July 17, 2014 5:03:26 AM
Subject: [R-SIG-Mac] consistent segfault
I can consistently get a segfault from Mavericks 3.1 and I suspect it
is from a mismatch
of compiled code
