-
-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
octave should have matching compilers availble #201376
Comments
This comment was marked as resolved.
This comment was marked as resolved.
Can you try doing /usr/bin/sed -i '' \
's/aarch64-apple-darwin23/aarch64-apple-darwin24/g' \
"$(brew --prefix octave)/lib/pkgconfig/octave.pc" and see if it helps? |
I tried it. Does not change anything. |
Yes, looks like the flags are baked into
|
Yes, the paths are built into |
Had the exact same issue. Tried the solution @carlocab suggested, thankfully it worked for me. Not sure why however. |
Since the linker flags contain references to Does that work? |
brew gist-logs <formula>
link ORbrew config
ANDbrew doctor
outputVerification
brew doctor
output saysYour system is ready to brew.
and am still able to reproduce my issue.brew update
and am still able to reproduce my issue.brew doctor
and that did not fix my problem.What were you trying to do (and why)?
For users to be able to install octave packages, the octave should be compiled with the same C/C+++/Fortran compilers
as on their systems. Currently there is a mismatch (at least for darwin24 systems), see e.g.
Homebrew/brew#18943 (comment)
What happened (include all command output)?
What did you expect to happen?
With self-compiled octave binary on the same system, it works fine:
Step-by-step reproduction instructions (by running
brew
commands)The text was updated successfully, but these errors were encountered: