-
Notifications
You must be signed in to change notification settings - Fork 0
ADBDEV-8376: Make Madlib build Greengage compatible #1
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
Conversation
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.
How do you plan to remove such Green(plum) mentions further? Maybe replace it with something like Green\w+ or pass as param for build system? (e.g. -DFORK_NAME)
Good idea and less diff! |
|
Is it expected that we still specify greenplum as the platform during installation? |
Yes, there is a related task for renaming. |
|
Are there any plans to actualize README.md and ReadMe_Build.txt for greengage? |
If you want to change something there, you can create a corresponding task. |
|
I could build it with greengage 7 with the commands: |
done |
|
I could run some tests with local greengage demo cluster on ubuntu 24. |
Make Madlib build Greengage compatible
Madlib 2 already supported Greenplum 6 and Greenplum 7. Add support for
Greengage 6 and Greengage 7:
Fix regular expressions in src/madpack/utilities.py,
src/ports/greenplum/cmake/FindGreenplum.cmake, and
src/ports/postgres/modules/utilities/utilities.py_in, and add additional
condition in src/madpack/madpack.py.
Madlib 2 only supports Python 3, remove specific environment variables from
src/madpack/madpack.py, and fix files src/madpack/sort-module.py,
src/ports/postgres/CMakeLists.txt, and src/CMakeLists.txt.
Fix an indent error in the src/ports/postgres/madpack/SQLCommon.m4_in file.
Ticket: ADBDEV-8376