Re: Leveraging gcc in a cross-compilation environment

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Philip A. Prindeville" <philipp_subx@xxxxxxxxxxxxxxxxxxxxx> writes:

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

gcc -v will show you this when compiling a file.

> * 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 ...")?

Same answer.

Ian

[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux