Older versions of postgresql would generate MAJVER.MINVER in new clusters. 10+ do not. Update the regex to determine PGMAJORVERSION as a single int.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Previously perl-native headers were erroneously included,
which was causing issues with the new perl recipe.
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The postgresql-setup utility log-in on postgres user to create the
database, however, the shell was set to bash and it wasn't being
installed as runtime dependency.
This rework this expectation to use busybox ash as shell and avoid the
new dependency
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Multiple -dbg packages per recipe is not encouraged, and only one is
recommended and the code only works properly in some cases for one.
Add RPROVIDES_${PN}-dbg to be compatiable with previous dbg packages
requiring.
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Postgreqsql was configured to use ossp-uuid but ossp-uuid is dead and everyone
will be building util-linux anyway, so use the libuuid.so from there.
Confusing the option is called e2fs because the library originated in e2fsprogs.
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
It fails to run command pg_config with segment fault. The root cause is
function sstate_hardcode_path takes elf file pg_config as a configure
file and edits it with 'sed'.
And then file pg_config is corrupt:
$ readelf -a package/usr/bin/pg_config >/dev/null
readelf: Error: Unable to read in 0x700 bytes of section headers
readelf: Error: Section headers are not available!
There is not other '*_config' file installed by postgresql except
pg_config, so remove '*_config' from SSTATE_SCAN_FILES for postgresql.
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
WARNING: postgresql-9.4.15-r0 do_patch:
Some of the context lines in patches were ignored. This can lead to incorrectly applied patches.
The context lines in the patches can be updated with devtool:
devtool modify <recipe>
devtool finish --force-patch-refresh <recipe> <layer_path>
Then the updated patches and the source tree (in devtool's workspace)
should be reviewed to make sure the patches apply in the correct place
and don't introduce duplicate lines (which can, and does happen
when some of the context is ignored). Further information:
http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148675.htmlhttps://bugzilla.yoctoproject.org/show_bug.cgi?id=10450
Details:
Applying patch remove.autoconf.version.check.patch
patching file configure.in
Hunk #1 succeeded at 19 with fuzz 2.
Now at patch remove.autoconf.version.check.patch
Signed-off-by: Armin Kuster <akuster808@gmail.com>
Zheng Ruoqin
Christophe PRIOUZEAU
Changqing Li
Zang Ruochen
Hongxu Jia
Adrian Bunk
Khem Raj
Akram Hameed
Alexander Kanavin
Otavio Salvador
Armin Kuster
Ross Burton
Kai Kang
Jackie Huang