Dirk Eddelbuettel

Let's hope it gets into the December release that will be the basis of the next BH release (following the pattern).

Oh, sorry to hear. Just had three of those myself in the last two weeks. And yes, local copy is best.

In `src/Makevars` (and `src/Makevars.win`) declare an additional include directory, maybe below `src/` itself. Store what you need from updated upstream Boost (as opposed to what my BH has from their...

Let us know how it goes, and if we can help. It would be good to have a worked example.

If you can use for example a Docker container, you can use that to get a Boost binary installation from a Linux distribution and use its `bcp` binary.

We now have Boost 1.87.0-0 in the main branch, and at R-universe. So you could try that to see if it helps with these build issues. You can follow #103...

Hm, that is frustrating. Modules can be finicky and prefer to have all compilation units compiled by the same compiler. Maybe in the CRAN instances it got mixed? It is...

BH 1.87.0-1 is now arriving at CRAN and should help with clang-19.

Release 1.0.13 should only cover what is in the repo right now, the rest will have to wait for 1.0.14. As you say, lots of moving parts still. (We could...

@ms609 Maybe start with your tests? I see ``` > library("testthat", warn.conflicts = FALSE) > library("TreeDist") > > test_check("TreeDist") Loading required package: ape *** caught segfault *** address 0x55b19059fec8, cause...