Hi Simon, Many thanks for your prompt reply and the link; it greatly helps, and I appreciate it!
Yes, sorry for not detailing my issue further, but I did not want to
spam anybody with the log and configuration files I am using, so I cut it
short.
I will also look more carefully into the differences between “my” build process
and the CRAN builds;
it seems evident that I have overlooked something. My initial thought was just
that with all the API
changes going on and me using a more recent version of macOS for the build than
CRAN does,
it would not surprise me that, at some point, something
had changed in macOS, causing this “user-interface-only” crash.
Anyway, so as not to bother you further, thanks again for the help. I am good
for now,
and if I figure out what has to be changed in my configuration to make it work
again, I will post it.
Kind regards,
Sebastian
> On 25. Sep 2024, at 01:40, Simon Urbanek <simon.urba...@r-project.org> wrote:
>
> Sebastian,
>
> if you want to replicate the CRAN builds, you have to also use the same
> settings, otherwise you may have a build which is not binary compatible. It
> is unclear from your description how you built R (there are several variants
> such as framework install vs "unix"-style install and they are incompatible).
> You can see the flags actually used at the top of ${R_HOME}/etc/Makevars.
>
> As for macOS R binaries, all latest builds are always available from
> https://mac.r-project.org/big-sur/last-success/
>
> The fact that the main page itself is not showing R-devel is certainly not
> intentional since the binaries are there - I’ll look into that, thanks for
> reposting (you shouldn't wait months to report that ;)).
>
> Thanks,
> Simon
>
>
>
>> On 24 Sep 2024, at 02:27, Sebastian Kreutzer
>> <sebastian.kreut...@uni-heidelberg.de> wrote:
>>
>> Hello,
>>
>> I am writing because I have been struggling for a couple of months to get
>> R-devel to work in combination with
>> RStudio or the R GUI.
>>
>> In the past, I had been downloading R-devel for macOS from
>> https://mac.r-project.org/, which
>> nearly always worked, however, for some (months I have in mind), there
>> aren't daily R-devel builds. So I started building
>> R from source following
>> https://stackoverflow.com/questions/75595875/how-do-i-build-r-from-sources-on-macos
>>
>> Adapted to my system, this worked surprisingly well, so I kept drawing
>> R-devel from the SNV server on a regular
>> basis and built it from the source. However, it stopped working in
>> mid-August. In a nutshell:
>>
>> - I can build R-devel from the source without any issue flagged, and when
>> started in the terminal, it works as expected.
>> - However, it crashes reproducibly when trying to load a package in RStudio
>> (stable/nightly build) and the R GUI (always the latest version)
>> terminates the R session on start. Error messages in the console I get read
>> as follows:
>>
>>> R GUI: Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault:
>>> 11
>>> RStudio: Exception Type: EXC_CRASH (SIGABRT) -> /usr/lib/dyld 0x0 -
>>> 0xffffffffffffffff ??? (*) <00000000-0000-0000-0000-000000000000> ???
>>
>> I can share the full logs, but I want to keep it short for now.
>>
>> My questions are:
>>
>> - Did anybody encounter such an issue with the latest R-devel and R GUI,
>> RStudio?
>> - Is this perhaps why an R-devel binary is currently not available on
>> https://mac.r-project.org/?
>>
>> If I know that this is a known issue, it is all good; however, if it works
>> For all others without, then the error must be on my end, and I have to keep
>> digging further.
>>
>> - Tested systems: M2 -> macOS 14.5 to 15.0 with the Xcode on always the
>> latest version available at the time.
>> - SNV: Always the latest check out
>>
>>
>> Kind regards,
>>
>>
>> Sebastian Kreutzer
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ R-SIG-Mac mailing list R-SIG-Mac@r-project.org https://stat.ethz.ch/mailman/listinfo/r-sig-mac
