{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 我想做一个坏孩纸 的问题《Create R binary packages for Linux that can be ins》','https://www.manongdao.com/q-523110.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I'm pretty sure this isn't possible, because if it were, then CRAN would have R Linux binary packages. Why isn't it possible? We can create Mac and Windows binary versions of R packages, and these tgz/zip files could be installed on different systems. Why can't we do the same for Linux?
I'm guessing because there are many different distros, and each distro is different. Is it possible to create binary files for Debian/Ubuntu and RHEL/CentOS?
If it's possible, how do we do it? Thanks.
Different compiler releases, different libc/libstc++ releases, different "other library" releases, different per-distro release cycles, ... make it that you just cannot match that goal with dynamic linking.
You can get half-way there as e.g. RStudio does by a) bundling all your depends and b) reflecting subsets as they do for Debian/Ubuntu and RH/FC/CentOS. But with a) the tarballs would get massive, as they would with static linking.
In short: you can't on Linux. So back to sources it is.