R is in general a self-contained universe, as far as I can see. There is a
mountain of packages that can be installed in the base system. In CRAN,
packages are generally compiled into PIC code, or so the site says, but new
versions of packages are often built from the R console, using the build
environment assumed by R.app. Building R.app on your own involves Xcode and
whatever libraries you want supported. CRAN provides a page full of compiled
libraries which install into /usr/local for use in local R builds.
I assume all of these issues have been resolved for CPAN for perl and
associated packages, but many R packages require compilation. Is that problem
similar for CPAN?
Anyway, at the moment, I’ve gone back to the CRAN distributed R.app and XQuartz
to try to build the package I want, within the distributed R environment.
Incidentally, there are alpha releases of XQuartz 2.8.0, being prepared by a
bloke with an Apple email address. That’s interesting.
Peter
--
Peter West
p...@pbw.id.au
And when his family heard it, they went out to seize him, for they were saying,
“He is out of his mind.”
> On 23 Jan 2021, at 8:31 am, Ken Cunningham
> wrote:
>
> If you’re trying to make a new port for something, and running into trouble,
> I would suggest you open a ticket for it as a “request” ticket, post up what
> you have, and we can work it through there if possible.
>
> If you’re trying to build something that is already in MacPorts, but doesn’t
> build for you, a ticket would be ideal.
>
> If you’re trying to build something on your own, unrelated to MacPorts, but
> using MacPorts parts, and it is not working, then show us the commands you’re
> using so far (exact series of commands, devil is in the details) and someone
> might be able to see what you need to do to get this working for you.
>
> Best,
>
> Ken
