diff options
| author | Michael Heimpold <mhei@heimpold.de> | 2023-06-03 17:57:18 +0200 |
|---|---|---|
| committer | Michael Heimpold <mhei@heimpold.de> | 2023-06-04 22:02:23 +0200 |
| commit | a2e76e49787e97253c02d72d27e3d304d68ff488 (patch) | |
| tree | e29e31187d9c7f9f79d8db4d7c46b1d6d9e080b0 /lang/python/python-asgiref | |
| parent | 97bc19b49cca44991569de41d73a864bdc723190 (diff) | |
php8: fix linking on riscv64 platform
The buildbots failed for the mentioned platform with the following error:
(I shortened the pathnames and broke long lines a little bit for readability)
.../lib/gcc/riscv64-openwrt-linux-musl/12.3.0/../../../../
riscv64-openwrt-linux-musl/bin/ld: Zend/zend_execute_API.o: in function `.L533':
zend_execute_API.c:(.text+0x1b1c): undefined reference to `__atomic_exchange_1'
.../riscv64-openwrt-linux-musl/bin/ld: Zend/zend_atomic.o:
in function `zend_atomic_bool_exchange':
zend_atomic.c:(.text+0xc): undefined reference to `__atomic_exchange_1'
collect2: error: ld returned 1 exit status
make[4]: *** [Makefile:350: sapi/cli/php] Error 1
Inspired by the blog post[1], linking to libatomic explicitly seems to
do the trick.
[1] A RISC-V gcc pitfall revealed by a glibc update
https://blog.jiejiss.com/A-RISC-V-gcc-pitfall-revealed-by-a-glibc-update
Signed-off-by: Michael Heimpold <mhei@heimpold.de>
Diffstat (limited to 'lang/python/python-asgiref')
0 files changed, 0 insertions, 0 deletions
