Cross-compiling is hard...
cross-compiled libgd installed its build/build_arm/staging_dir/usr/bin/gdlib-config
that gtlib-config is going to be part of the target system image, so it thinks libgd's headers are in /usr/include
they're in build/build_arm/staging_dir/usr/include, which will become /usr/include in the target system
then I'm cross-compiling a package which depends on libgd
its ./configure calls that gdlib-config
and adds -I/usr/include to its CFLAGS
host's /usr/include
how has this ever worked?
Follow
I don't know your setup, but in the past I used to intercept calls to annoying tools with properly named scripts in the PATH that did what I wanted them to do.
@Shamar I'd rather keep my hax and patches in line with what buildroot does...
so patching the source before build or adding env vars is way easier than adding another binary to PATH