-
Notifications
You must be signed in to change notification settings - Fork 236
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
added compatibility with Flint 3.1.0 #3152
added compatibility with Flint 3.1.0 #3152
Conversation
I'm still getting a build error with FLINT 3.1.0 after applying this patch:
|
Yea I realized it's not enough. I'm evaluating how twisted of a solution is warranted here (e.g. a macro that repeats a variable depending on version of flint, or just a bunch of if/elses) |
645ab54
to
4f4146b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this compiles under flint 3.1.0, it looks good (and a simple fix too).
I was getting ready to look at this, but it looks like you have it done! Is this all set possibly? I'll look at the changes you made, actually, just did, looks good. It looks like it is not running builds though. @DanGrayson, should I just accept it? |
This branch isn't set up to have tests. I don't really understand why there's a separate branch for the release. Everything should be happening on |
@mahrud If I update brew now, it will install flint 3.1.0, and remove the old version? So if I want to keep doing development on other branches, I'll need to cherry pick these fixes in to these branches? |
Not to mention that this commit is will be missing from development, so you'd need to merge this branch into development, adding an entirely unnecessary merge commit. |
I'm still getting an error:
|
The builds worked locally for me and also here on ubuntu and macOS: Macaulay2/homebrew-tap#217 |
The |
@d-torrance I'll take a look. Is this the only commit so far tying to fix flint 3.1.0 use? @mahrud @DanGrayson @d-torrance Maybe we could streamline build release branches/tags. We should discuss what we can do to streamline the build process, especially if the two of you (or a subset, or others too) will be doing releases going forward. |
I think I'll plan on localizing all use of ffpack and givaro to one file (that doesn't have flint either). This will entail removing ARing types from FFPACK and Givaro (or rather, using them in one file only, for computing rank of a dense matrix over a prime finite field. This will not be for this release. |
@d-torrance This appears in aring-zzp-flint.hpp. I don't see the define anywhere. Do you know how this is being set?
edit: nevermind, I didn't grep far enough up the food chain, it os being set during configure time. It certainly seems that on the machine where the failure is occuring, it is either not including this file, or if so, it isn't any longer referring to these functions? |
Mike, I think you're right! The autotools build only sets that |
Yup, that did the trick! I'm still getting those |
The |
I didn't realize that was the plan. Is this the expectation for this release? |
Should we update the FLINT submodule to point to 3.1.0? (Not necessarily for the release, but maybe for the On a related note, I haven't forgotten that I volunteered to update the autotools build to use the submodule a few months ago. :) |
@mahrud I think maybe going forward, but not for this release (I only said you are part of the group doing releases, because you are creating the brew Macaulay2 release each time already...) |
No description provided.