Skip to content

Transition to Eigen 5.0.* #151

Description

@eddelbuettel

Issue #143, filed late last year, raised the question of whether, or when, we would get to Eigen 5.0.*. As detailed in the nearly 100 messages in that issue, it took a while.

As of September 2026, and thanks to the stan team, we can build against a very large number of packages---but a rather large number remains problematic. Per a reverse dependency run (summarised here), we now '472 successes, 69 failures, 24 skipped'. This issue will aim to regroup in sub-issues the required work on different packages. As of right now, one PR has been filed, and more will follow.

Help is definitely welcome.

If you can work on one of the packages, please do. In general the CRAN version 0.3.4.0.2 passes for the CRAN dependencies, and the candidate version 0.4.9.9-2 at r-universe (and here at GitHub) represents the release candidate with Eigen 5.0.1 which breaks some packages. The key will to adjust the affected packages to that they still build under the CRAN and the r-universe version permitting a smooth upgrade of the RcppEigen package.

Individual packages:

More to follow, see full list

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions