Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: Even more problems with lcc-win Date: Fri, 24 Mar 2017 09:37:52 -0700 Organization: None to speak of Lines: 35 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="942005ccab53837d4f31c6c0d31e9033"; logging-data="32258"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18hj7NAWEA3Hd+rMYFdPdv2" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:GFID/vD3LeBR5q92xDQZ49h/jcM= sha1:gV8eidFiLvFxVHgUsv9xZCLfHlY= Xref: csiph.com comp.lang.c:106941 jacobnavia writes: > I am starting to get results with my ARM64 port. lcc-win is compiling > big programs now, without any problems... > > The acid test is to compile the compiler with itself. To do that, I need > to parse the includes furnished by the linux system/gcc. There is a > confusing mixture of include files in > /usr/include, > /usr/include/aarch64/bits, > /usr/local/include/aarch64, > > and a LONG list of "places" where includes with the same name are stored. > > Which one should I use? How could I figure out which ones are used by gcc? By asking gcc. Compile some random source file with "gcc -v". On my system, I get: ignoring nonexistent directory "/usr/local/include/x86_64-linux-gnu" ignoring nonexistent directory "/usr/lib/gcc/x86_64-linux-gnu/6/../../../../x86_64-linux-gnu/include" #include "..." search starts here: #include <...> search starts here: /usr/lib/gcc/x86_64-linux-gnu/6/include /usr/local/include /usr/lib/gcc/x86_64-linux-gnu/6/include-fixed /usr/include/x86_64-linux-gnu /usr/include End of search list. -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"