Open MichaelChirico opened 10 months ago
@MichaelChirico These are good suggestions esp. make clean
. A FAQ page for troubleshooting in the guides would make good sense.
The recent R dev day resulted on a couple of issues, feedback #175 and #174. There is also some more feedback at #173 .
Now that the guide is getting more usage maybe it is time to add this?
Also it is worth mentioning svn cleanup --vacuum-pristines --remove-ignored --remove-unversioned
to remove everything from the source repository (in case there are some other files or old files).
This will require to download packages again via ./tools/rsync-recommended
which would have fixed the original issue.
I came across two failures running
make
today that interrupted my usual workflow for building r-devel.I wondered if keeping something like an FAQ for troubleshooting R builds would make sense for the guide. Or perhaps it could just be a Wiki document on this repo that's pointed to by the guide, to make contribution less intensive?
To get things started here were the two fixes I needed today:
Run
make clean
to reset stateSometimes the compiled
.o
/.so
files from previousmake
runs get stale withoutmake
realizing it and re-compiling on its own.In such cases, running
make clean
before re-tryingmake
may be the only way to proceed. Here's the error I encountered today:I first checked around for where
libicuuc
is coming from (ICU library, mentioned in R-admin, installed as e.g.apt-get install libicu-dev
on Ubuntu), and made sure I have it installed, which I do, meaning something "funny" is going on and hinting at the need for amake clean
.Needed to update my copies of the Recommended packages
I only ran the required
./tools/rsync-recommended
once, long ago when I first set up my local copy of the SVN repo -- looks like circa 2021.I turns out my old copies of these packages have drifted far enough from the current versions that they now fail to compile. Here's the error I encountered during
make
:(and dozens more compiler errors like that).
I was trying to find where the
Sint
type is defined and happened to look at the current CRAN version of MASS:https://github.com/cran/MASS/blob/ba503858f613cfb21fae8e539e4c5bd81da1c10e/src/MASS.c#L38-L39
That
Sint
type is no longer used. That clued me in to "maybe my version of MASS is too old" and discovered I needed to run./tools/rsync-recommended
again.Overall, it would be nice to have a "canonical" place to refer to for troubleshooting builds with common (or not-so-common!) issues recorded.