Displaying 2 results from an estimated 2 matches for "ptr_r_processevents".
2024 Dec 12
2
R3.4 on Debian12
...0x0): multiple definition of `R_OutputCon'; CommandLineArgs.o:(.bss+0x0): first defined here
/usr/bin/ld: ../unix/sys-unix.o:(.bss+0x0): multiple definition of `R_OutputCon'; CommandLineArgs.o:(.bss+0x0): first defined here
/usr/bin/ld: ../unix/sys-unix.o:(.bss+0x8): multiple definition of `ptr_R_ProcessEvents'; ../unix/system.o:(.bss+0xa8): first defined here
/usr/bin/ld: ../unix/X11.o:(.bss+0x0): multiple definition of `R_OutputCon'; CommandLineArgs.o:(.bss+0x0): first defined here
/usr/bin/ld: connections.o: warning: relocation against `R_OutputCon' in read-only section `.text'
/usr/bi...
2017 Jan 25
2
parallel::mc*: Is it possible for a child process to know it is a fork?
When using multicore-forking of the parallel package, is it possible
for a child process to know that it is a fork? Something like:
parallel::mclapply(1:10, FUN = function(i) { test_if_running_in_a_fork() })
I'm looking into ways to protect against further parallel processes
(including threads), which not necessarily are created via the
parallel:mc* API, are being spawned off recursively.