Leveraging gcc in a cross-compilation environment

["Philip A. Prindeville" <philipp_subx at redfish-solutions dot com>]

Hi.

I'm using "gcc" with an old version of buildroot, and I'm trying to figure out a few best practices for having the cross-compiler look at the target's header files and libraries, and not the build host's.

For instance,

* how (on a somewhat hinky, tweaked compiler) do I figure out where it looks for system headers by default?

* and when additional arguments get added (--sysroot, -isysroot, -isystem, -iquote, etc) how do I figure out where the compiler is looking for headers and libraries (short of "strace -f -e trace=open,stat,fstat,lstat,access gcc ...")?

Is there a good document that covers all of these options and more (maybe -stdinc, etc. as well)?

Thanks,

-Philip