Am Montag, 15. Mai 2006 23:52 schrieb Dan Nicholson: > On 5/15/06, Dan Nicholson <[EMAIL PROTECTED]> wrote: > > $ /sources/gcc-build/gcc/xgcc -v dummy.c | grep include > > I just figured out something simpler to see the header search path. > xgcc is just a frontend for the actual driver, cc1. This guy actually > gets executed when compiling or preprocessing and seems to find the > headers for you. > > Try this command
OK, I'll try it. > $ echo | /sources/gcc-build/gcc/cc1 -v To my surprise it seeems to work. > Should tell you where xgcc is looking for headers. echo | /sources/gcc-build/gcc/cc1 -v ignoring nonexistent directory "/usr/lib/gcc/i686-pc-linux-gnu/4.0.3/include" ignoring nonexistent directory "/usr/lib/../i686-pc-linux-gnu/include" #include "..." search starts here: #include <...> search starts here: /usr/local/include End of search list. Execution times (seconds) TOTAL : 0.01 0.00 0.04 Note: "/usr/local/include" is just empty. > -- > Dan Leonhard -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
