Skip to content

Octave: Use c++ 17 #618

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.

Sign up for GitHub

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

Jump to bottom
Merged
jschueller merged 1 commit into from
Jun 18, 2025
Merged

Octave: Use c++ 17 #618

jschueller merged 1 commit into from
Jun 18, 2025
+4 −0

Conversation

@jschueller
Copy link
Collaborator

@jschueller jschueller commented Jun 8, 2025

see #616

@jschueller jschueller merged commit a75f3d9 into stevengj:master Jun 18, 2025
3 checks passed
@jschueller jschueller deleted the octave10 branch June 18, 2025 17:46
@opoplawski
Copy link
Contributor

opoplawski commented Aug 1, 2025

This patch does not appear to be working for me in Fedora rawhide with octave 10.1.0. I still end up with -std=gnu++11. I that version logic really correct?

@jschueller
Copy link
Collaborator Author

jschueller commented Aug 1, 2025 •
edited
Loading

you need #597 that removed the explicit c++11 standard,
then for fedora no need for #618 because default standard is already c++17 or higher with gcc 15

@jschueller
Copy link
Collaborator Author

jschueller commented Aug 1, 2025 •
edited
Loading

@stevengj maybe we could release a 2.10.1 for the octave fixes, what do you think ?

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

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@jschueller @opoplawski