Skip to content

Linbox patch #40066

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Linbox patch #40066

wants to merge 1 commit into from

Conversation

edgarcosta
Copy link
Member

@edgarcosta edgarcosta commented May 7, 2025

This patch fixes on OSX

[spkg-install] ../../linbox/vector/blas-subvector.h:121:20: error: no member named 'data' in 'BlasSubvector<_Vector>'
[spkg-install]   121 |             _ptr(V.data()+beg), _size(dim), _inc(inc), _field(&V.field()) {}
[spkg-install]       |                  ~ ^
g++ -std=gnu++11 -g -O2 -Isage/libs/flint -I/Applications/sage/src -I/Applications/sage/local/var/lib/sage/venv-python3.13/lib/python3.13/site-packages/numpy/_core/include -I/opt/homebrew/opt/[email protected]/Frameworks/Python.framework/Versions/3.13/include/python3.13 -I/Applications/sage/local/var/lib/sage/venv-python3.13/include -I/opt/homebrew/opt/[email protected]/Frameworks/Python.framework/Versions/3.13/include/python3.13 -c sage/libs/linbox/linbox_flint_interface.cpp -o build/temp.macosx-15.0-arm64-cpython-313/sage/libs/linbox/linbox_flint_interface.o -DDISABLE_COMMENTATOR -DFFLAS_COMPILED -DFFPACK_COMPILED -std=gnu++11
    In file included from sage/libs/linbox/linbox_flint_interface.cpp:1963:
    In file included from /Applications/sage/local/include/linbox/solutions/charpoly.h:34:
    In file included from /Applications/sage/local/include/linbox/algorithms/bbcharpoly.h:46:
    In file included from /Applications/sage/local/include/linbox/solutions/det.h:608:
    In file included from /Applications/sage/local/include/linbox/algorithms/det-rational.h:41:
    In file included from /Applications/sage/local/include/linbox/algorithms/last-invariant-factor.h:30:
    In file included from /Applications/sage/local/include/linbox/algorithms/rational-solver.h:583:
    In file included from /Applications/sage/local/include/linbox/algorithms/./dixon-solver/dixon-solver-dense.h:363:
    In file included from /Applications/sage/local/include/linbox/algorithms/./dixon-solver/./dixon-solver-dense.inl:26:
    In file included from /Applications/sage/local/include/linbox/algorithms/lifting-container.h:49:
    In file included from /Applications/sage/local/include/linbox/blackbox/block-hankel-inverse.h:36:
    /Applications/sage/local/include/linbox/blackbox/block-hankel.h:348:23: error: no member named '_coldim' in 'BlockHankel<_Field>'; did you mean 'coldim'?
      348 |                         linbox_check(this->_coldim == y.size());
          |                                            ^~~~~~~
          |                                            coldim

By applying:
linbox-team/linbox@4a1e139?w=1#diff-6344b04fac6de3b0e7ff00458910d867c9ee947aff5797a459c0e2c9403da1f4L118-L124)
Mentioned here linbox-team/linbox#320

and a subset of linbox-team/linbox#323

Copy link

github-actions bot commented May 7, 2025

Documentation preview for this PR (built with commit c2c0ca8; changes) is ready! 🎉
This preview will update shortly after each push to this PR.

@dimpase
Copy link
Member

dimpase commented May 9, 2025

isn't it included here: #39985 ?

Copy link
Member

@dimpase dimpase left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's already in a positively reviewed PR

@dimpase
Copy link
Member

dimpase commented May 9, 2025

sorry, you could have at least searched for the recent PRs saying linbox in the subject (and reviewed them)

@edgarcosta
Copy link
Member Author

sorry. the frustration battling the build system won over me.

@dimpase
Copy link
Member

dimpase commented May 9, 2025

Never mind. It seems that we need a better organisation of the routine parts of the development process. E.g. even if someone posts a PR to fix the build issues, and even posts a link to it on one of our google groups, noone is keen on reviewing it. Or people start reviewing, find they it's only a partial fix, and stall.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants