diff options
| author | Changqing Li <changqing.li@windriver.com> | 2025-02-13 17:23:06 +0800 |
|---|---|---|
| committer | Khem Raj <raj.khem@gmail.com> | 2025-02-13 07:44:16 -0800 |
| commit | cdd8b41d6e3b20ca562df49aa0710f07a6218f20 (patch) | |
| tree | 272520243d3926f4d6638cab3c02b7570f493eb2 /meta-python/recipes-devtools/python/python3-aiohttp-jinja2_1.6.bb | |
| parent | f06a439827fb3ec6839f447c5fde2b777c48c982 (diff) | |
| download | meta-openembedded-cdd8b41d6e3b20ca562df49aa0710f07a6218f20.tar.gz | |
mariadb: correct STACK_DIRECTION setting
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>
Diffstat (limited to 'meta-python/recipes-devtools/python/python3-aiohttp-jinja2_1.6.bb')
0 files changed, 0 insertions, 0 deletions