summaryrefslogtreecommitdiffstats
path: root/meta-python/recipes-devtools/python/python3-aws-iot-device-sdk-python
diff options
context:
space:
mode:
authorGyorgy Sarvari <skandigraun@gmail.com>2025-01-25 13:44:19 +0100
committerKhem Raj <raj.khem@gmail.com>2025-01-25 09:36:50 -0800
commita91f294b1e55cb6caa3c8b8b6c94b0d05ed9bc22 (patch)
tree85909bb528af23c07801b8a80edc39748c36d79a /meta-python/recipes-devtools/python/python3-aws-iot-device-sdk-python
parenta921c95a5778411ce69ea567a20035e0c154a7a5 (diff)
downloadmeta-openembedded-a91f294b1e55cb6caa3c8b8b6c94b0d05ed9bc22.tar.gz
python3-posix-ipc: use correct C compiler to detect system features
During compilation, prober.py (called from setup.py) uses "cc" to compile some simple code, to detect if the used features are available. However during cross-compilation we don't use "cc", but some other compiler for cross-compiling. Due to this, the feature detection can fail (maybe it fails always?), as the correct C compiler for Yocto is not cc, but the content of CC environment variable. To solve this, instead of using cc always, take the C compiler from the CC environment variable when it is available, and fall back to cc only when this environment variable is not set. Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
Diffstat (limited to 'meta-python/recipes-devtools/python/python3-aws-iot-device-sdk-python')
0 files changed, 0 insertions, 0 deletions