[strace/strace] building strace with buildroot fails when a toolchain is installed on the system (#150)

Dmitry V. Levin notifications at github.com
Mon Sep 7 08:38:00 UTC 2020

> 	D="" \
> 	READELF="/srv/storage/hthiery/buildroot/output/host/bin/aarch64-buildroot-linux-gnu-readelf" \
> 	CC="arm-linux-gnueabi-gcc" \
> 	CFLAGS="-DHAVE_CONFIG_H   -I./linux/aarch64 -I./linux/aarch64 -I./linux -I./linux -I. -I.      -DMPERS_IS_m32" \
> 	CPP="/srv/storage/hthiery/buildroot/output/host/bin/aarch64-buildroot-linux-gnu-cpp" \
> 	CPPFLAGS="-DHAVE_CONFIG_H   -I./linux/aarch64 -I./linux/aarch64 -I./linux -I./linux -I. -I.      -DIN_MPERS -DMPERS_IS_m32" \
> 	./mpers.sh m32 "-std=gnu99 " $f || exit; \

CPP doesn't match CC, this doesn't look correct.

> mpers-m32/kernel_v4l2_buffer_t.c:16:23: error: invalid application of 'sizeof' to incomplete type 'struct v4l2_meta_format'

Apparently, here it uses host kernel headers instead of the target ones, and the former don't provide a definition of struct v4l2_meta_format while the latter do.

This is likely a strace configure issue.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.strace.io/pipermail/strace-devel/attachments/20200907/3a923758/attachment.htm>

More information about the Strace-devel mailing list