gcc: Pull in libstdc++ getentropy usage fix #526
Conversation
stephanosio
added
the
area: libstdc++
|
DNM until zephyrproject-rtos/gcc#8 is merged and the commit reference is updated in this PR. |
stephanosio
force-pushed
the
fix_libstdcxx_getentropy
branch
from
c4db5d4 to
2f6224b
Compare
This commit pulls in the GCC patch that fixes the problem in which the libstdc++ incorrectly picks up the availability of the "getentropy" and "arc4random" functions and uses them for "std::random_device" leading to "undefined reference to `getentropy`" link errors. Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
stephanosio
force-pushed
the
fix_libstdcxx_getentropy
branch
from
2f6224b to
56431d1
Compare
There was a problem hiding this comment.
Tested by running tests/subsys/cpp/libcxx at stephanosio/zephyr@bc4dd7d
The tests/subsys/cpp/libcxx/cpp.libcxx.newlib fails to link for qemu_cortex_a53 with the following error message:
/home/stephanos/Downloads/test2/zephyr-sdk-0.15.0-beta2-2-g2f6224b/aarch64-zephyr-elf/bin/../lib/gcc/aarch64-zephyr-elf/12.1.0/../../../../aarch64-zephyr-elf/bin/ld.bfd: discarded output section: `.got.plt'
collect2: error: ld returned 1 exit status
The above link failure is unrelated to the change in this PR and likely has to do with a behavioural change in the recenet Binutils releases.
A similar issue observed and fixed in the Linux kernel:
https://www.spinics.net/lists/kernel/msg3571205.html
To be fixed later during the Zephyr integration stage since this is not a Zephyr SDK issue.
This commit pulls in the GCC patch that fixes the problem in which the
libstdc++ incorrectly picks up the availability of the "getentropy" and
"arc4random" functions and uses them for "std::random_device" leading
to "undefined reference to
getentropy" link errors.Signed-off-by: Stephanos Ioannidis root@stephanos.io
GCC PR: zephyrproject-rtos/gcc#8
Fixes #519