public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Kai Ruottu <kai.ruottu@luukku.com>
To: Meir Hacohen <meir.hacohen@telrad.co.il>
Cc: crossgcc@sources.redhat.com
Subject: Re: problem installing gcc 2.95.2 on m68k-coff  (fwd)
Date: Mon, 25 Sep 2000 12:31:00 -0000	[thread overview]
Message-ID: <39CF6C2C.629C42ED@luukku.com> (raw)
In-Reply-To: <Pine.GHP.4.10.10009251110490.2618-100000@tlhuph21>

Meir Hacohen wrote:
> 
>   Thanks for the help. I use the option 'make CFLAGS="-v -O2"' and I
> found, that there is no search list for the include "... " . How can I
> solve this problem.

 Another interpretation could be that the search lists are identical.

 If quoting the GNU cpp manual:

---------------------- clip ------------------------------------
#include "file"
This variant is used for header files of your own program.  It searches
for a file named file first in the current directory, then in the same
directories used for system header files.  The current directory is the
directory of the current input file.  It is tried first because it is
presumed to be the location of the files that the current input file
refers to.  (If the -I- option is used, the special treatment of the
current directory is inhibited.)
---------------------- clip ------------------------------------

 So my memory about using the '"'s around the header names was wrong,
using them causes searching also from the system headers.

> Following is the relevant output :
> 
> GNU CPP version 2.95.2 19991024 (release) (hppa)
> #include "..." search starts here:
> #include <...> search starts here:
>  .
>  ../../gcc-2.95.2/gcc
>  ../../gcc-2.95.2/gcc/config
>  ../../gcc-2.95.2/gcc/../include
>  /usr/local/include
> 
> /usr/local/lib/gcc-lib/hppa1.1-hp-hpux10.20/2.95.2/../../../../hppa1.1-hp-hpux1
> 0.20/include
>  /usr/local/lib/gcc-lib/hppa1.1-hp-hpux10.20/2.95.2/include
>  /usr/include

 The first four come from the '-I' options on the GCC command line...

 So these seem to be quite ok for a native compiler, although the one
with the 'relative path' may cause some questions, e.g. quite many
Linux-distributions may have it symlinked to the standard headers in
'/usr/include', and not as an empty directory for some extra headers,
as the purpose for it seems to be. A cross-compiler has the standard
target headers there, so it will be included last.

Cheers, Kai



------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

      reply	other threads:[~2000-09-25 12:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-21  7:26 Meir Hacohen
2000-09-21 13:06 ` Kai Ruottu
2000-09-24  7:25   ` Meir Hacohen
2000-09-25 12:31     ` Kai Ruottu
2000-10-26  6:24       ` problem installing gcc 2.95.2 on m68k-coff Meir Hacohen
2000-10-27  4:13         ` Kai Ruottu
2000-10-31  1:28           ` Meir Hacohen
2000-09-25  1:14   ` problem installing gcc 2.95.2 on m68k-coff (fwd) Meir Hacohen
2000-09-25 12:31     ` Kai Ruottu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=39CF6C2C.629C42ED@luukku.com \
    --to=kai.ruottu@luukku.com \
    --cc=crossgcc@sources.redhat.com \
    --cc=meir.hacohen@telrad.co.il \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).