ERROR: Make install error on Centos7.9

[Zhangbaowen-Hashdata]

Cloudberry Database version

No response

What happened

Make install error on Centos7.9 during manual compilation according to readme documentation

What you think should happen instead

No response

How to reproduce

Check to see if there is a problem with the file
eg: Makefile.

Operating System

centos7.9

Anything else

No response

Are you willing to submit PR?

• Yes, I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct.

[github-actions]

Hey, @Zhangbaowen-Hashdata welcome!🎊 Thanks for taking the time to point this out.🙌

[avamingli]

Got similar issue on Ubuntu, even after cherry-pick fixes from #386

Makefile:36: warning: overriding recipe for target 'installcheck'
Makefile:31: warning: ignoring old recipe for target 'installcheck'
/usr/bin/install: missing destination file operand after '/home/gpadmin/install/gp9/lib/python/gppylib/data/'
Try '/usr/bin/install --help' for more information.
make[4]: *** [Makefile:17: install] Error 1
make[3]: *** [Makefile:8: install-data-recurse] Error 2
make[3]: *** Waiting for unfinished jobs....
make[2]: *** [Makefile:13: install-gppylib-recurse] Error 2
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile:7: install-bin-recurse] Error 2
make: *** [GNUmakefile:74: install] Error 2

@Ray-Eldath

./configure --prefix=/home/gpadmin/install/gp9 --enable-debug --enable-cassert --with-perl --enable-tap-tests
gpadmin@i-v3roa8c2:~/work/gp9$ python --version
Python 3.10.6

[Ray-Eldath]

This has been resolved. with new release v1.5.0 the tag breaks the convention of version numbers that getversion and many scripts dependent upon (there shouldn't be a v prefix). as a temporary fix, one should run git tag -a -m "" 1.5.0 v1.5.0 after cloning the repo to forcibly correct this until a permanent fix has been carried out.

[tuhaihe]

After updating the tags, the Cloudberry Database can now be built successfully. You can try it again. @avamingli

[tuhaihe]

I believe we have resolved this issue. If not, please let us know and we will reopen it.