-
Notifications
You must be signed in to change notification settings - Fork 421
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
In Greenplum, compiling the AGE plugin fails with the error: 'void value not ignored as it ought to be #1975
Comments
I noted your mentioning underlying PG version is 12, it would be nice if you could confirm running pg_config tool from the bin subdirectory ( if it is present, I found GreenPlum hard to install following Broadcom site, so, more info regarding environment would help to build confidence in troubleshooting steps ). |
thanks for taking a look. @MironAtHome Below are the results of pg_config execution: I changed the statement return errmsg("%s at end of input", msg); to return 0;. Now the compilation issue is resolved, and I made similar modifications in a few other places. |
Describe the bug
Hi! I am trying to integrate the AGE plugin into Greenplum. Since Greenplum 7 is based on PostgreSQL 12, I think it should be compilable and usable. I used the version package of age-PG12-v1.5.0-rc0, but I encountered an error when compiling AGE separately. What is the problem? Or does AGE not support the Greenplum 7 database?
How are you accessing AGE (Command line, driver, etc.)?
none
What data setup do we need to do?
compile
What is the necessary configuration info needed?
pg_config
make install
What is the command that caused the error?
Expected behavior
Compilation successful
Environment (please complete the following information):
Linux version 3.10.0-1160.119.1.el7.x86_64 (mockbuild@kbuilder.bsys.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-44) (GCC) ) #1 SMP Tue Jun 4 14:43:51 UTC 2024
gcc version 8.5.0 (GCC)
flex 2.6.1
bison (GNU Bison) 3.0.4
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: