The component itself builds just fine with CMake 4, but the tests don't as they
rely on a bundled version of GTest that is six years old. Since upstream is
inactive, the simplest course of action is to apply the 'minimum policy version'
override (as implemented in CMake, it only affects the GTest submodule).
System GTest can not be used instead (easily), as among other things it requires
C++14 and the project uses C++11.
Signed-off-by: Moritz Haase <Moritz.Haase@bmw.de>
CC: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Use the GO_SRCURI_DESTSUFFIX convenience variable for the Go main module
in the SRC_URI variable.
Signed-off-by: Christian Lindeberg <christian.lindeberg@axis.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Removing all the S = ${WORKDIR}/git assignments works because BB_GIT_DEFAULT_DESTSUFFIX
is set to match S from bitbake.conf (which itself is set to match typical tarball
releases).
ERROR: influxdb-1.8.10-r0 do_unpack: Recipes that set S = "${WORKDIR}/git" or S = "${UNPACKDIR}/git" should remove that assignment, as S set by bitbake.conf in oe-core now works.
Signed-off-by: Alper Ak <alperyasinak1@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Use the go module fetcher instead of allowing network access during the
compile task.
Apply patch to replace github.com/pkg/term with github.com/kraj/term
unconditionally to avoid conditional module dependencies.
Reorder variables according to the recipe style guide.
Signed-off-by: Christian Lindeberg <christian.lindeberg@axis.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Please see
https://git.yoctoproject.org/poky/commit/?id=4dd321f8b83afecd962393101b2a6861275b5265
for what changes are needed, and sed commands that can be used to make them en masse.
I've verified that bitbake -c patch world works with these, but did not run a world
build; the majority of recipes shouldn't need further fixups, but if there are
some that still fall out, they can be fixed in followups.
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Latest layer compatibility checks have been enhanced to check for
network access during non-fetch tasks and flag it as failure, which
is now happening for these recipes since it calls go module fetcher
during do_compile
Latest gomod fetcher has got improvements and can be used for these
recipes but it needs some work. Skip them until it is fixed
Signed-off-by: Khem Raj <raj.khem@gmail.com>
configure: make sure to call AC_CHECK_HEADER_STDBOOL before using ac_cv_sizeof_bool
It was called after this conditional, so PG_USE_STDBOOL wasn't set
even when it should be as shown in at the end of config.log:
ac_cv_header_stdbool_h=yes
ac_cv_sizeof_bool=1
ac_cv_type__Bool=yes
#define SIZEOF_BOOL 1
#define HAVE__BOOL 1
#define HAVE_STDBOOL_H 1
* fixes:
https://github.com/postgresql-interfaces/psqlodbc/issues/110https://github.com/postgresql-interfaces/psqlodbc/issues/94http://errors.yoctoproject.org/Errors/Details/852841/
In file included from ../psqlodbc-16.00.0000/environ.h:16,
from ../psqlodbc-16.00.0000/environ.c:16:
../psqlodbc-16.00.0000/psqlodbc.h:264:23: error: 'bool' cannot be defined via 'typedef'
264 | typedef unsigned char bool;
| ^~~~
Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This is a major version upgrade, see release note:
https://www.postgresql.org/docs/release/
* Refresh patches:
0003-configure.ac-bypass-autoconf-2.69-version-check.patch
0005-postgresql-fix-ptest-failure-of-sysviews.patch
* Removed dropped option --enable-thread-safety
* Add depends for bison-native
* Fix do_packge_qa error:
*.c *.h generated by bison or flex leave full paths in comment,
rewrite those before *-src packaging
Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Set correct pkgconfig directory via INSTALL_PCDIR, otherwise on 64-bit
targets, the .pc file will be installed to /usr/lib64/pkgconfig by
default.
Signed-off-by: Yi Zhao <yi.zhao@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Set pam module path to ${base_libdir}/security via INSTALL_PAMDIR. Then
we can get rid of the workaround in do_install.
Signed-off-by: Yi Zhao <yi.zhao@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
STACK_DIRECTION = 1 means stack grow upwards
STACK_DIRECTION = -1 means stack grow downwards
In the majority of modern architectures, stack grows downwards. So set
STACK_DIRECTION = 1 is not right. But the failure is not exposed before,
mysqld can start normally, and simple runtime operation like create db,
table, select info, works well. But it is exposed after commit [1] is
merged, mysqld will start failed with error:
2025-02-12 3:18:19 0 [ERROR] Could not open mysql.plugin table: "Thread stack overrun: 16752824 bytes used of a 299008 byte stack, and 81920 bytes needed
Since commit [2], mariadb started to determine the default
STACK_DIRECTION in CMake based on the ISA, and we have set correct
CMAKE_SYSTEM_PROCESSOR in cmake.bbclass, so just don't pass it.
[1] https://github.com/MariaDB/server/commit/bddbef3573349b0565c43c27beba47c89358f39f
[2] https://github.com/MariaDB/server/commit/d0abbdf56e11ccc88447c1dc80caaf355c94be3b
[3] https://jira.mariadb.org/browse/MDEV-36051
Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Drop 0001-Use-a-lambda-function-as-deleter-prototype-in-unique.patch its
already in this version
Drop ppc musl patch, a check for glibc is already added in this version
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Set pam module path to ${base_libdir}/security as this is the default
path in libpam.
Signed-off-by: Yi Zhao <yi.zhao@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The pmem_cvap() function currently uses the '.arch armv8.2-a' directive
for the 'dc cvap' instruction. This will cause build errors below when
compiling for ARMv9 systems. Update the '.arch' directive to 'armv9.4-a'
to ensure compatibility with ARMv9 architectures.
{standard input}: Assembler messages:
{standard input}:169: Error: selected processor does not support `retaa'
{standard input}:286: Error: selected processor does not support `retaa'
make[2]: *** [storage/innobase/CMakeFiles/innobase_embedded.dir/build.make:
1644: storage/innobase/CMakeFiles/innobase_embedded.dir/sync/cache.cc.o]
Error 1
Signed-off-by: Ruiqiang Hao <Ruiqiang.Hao@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Replacing P with BP to fix following do_package_qa error for lib32-postgresql:
ERROR: QA Issue: File /usr/src/debug/lib32-postgresql/16.4/src/pl/plperl/SPI.c in package lib32-postgresql-src contains reference to TMPDIR [buildpaths]
Signed-off-by: Changqing Li <changqing.li@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Modify the CMakeLists.txt to add an Option for
STATIC target import, as available for shared library.
Link: https://github.com/facebook/rocksdb/pull/12890
Configure static library default to switched off
as shared libraries are sufficient in most cases.
Signed-off-by: Bhabu Bindu <bindu.bhabu@kpit.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Currently, any non-native recipes that inherits cpan-base ends up
with an image RDEPENDS on perl (via
https://git.yoctoproject.org/poky/tree/meta/classes-recipe/cpan-base.bbclass?h=scarthgap#n14)
If you are building an image and desire to have Postgresql installed
but NOT perl, this creates a problem. This changeset attempts
to fix this shortcoming by not inheriting cpan-base directly.
Note this work is a continuation of attempts to change cpan-base:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=15563
The Postgresql build system uses perl, so add it as a DEPENDS. This
happened previously via the "inherit cpan-base" directive.
I've validated this recipe successfully packages with and without
the perl PACKAGECONFIG in Scarthgap.
Signed-off-by: Barry Grussling <mr.scada@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Replace references of WORKDIR with UNPACKDIR where it makes sense to do
so in preparation for changing the default value of UNPACKDIR.
Signed-off-by: Khem Raj <raj.khem@gmail.com>