Re: Search paths

[Jeffrey A Law <law@cygnus.com>]

  In message < 199807021533.RAA21650@jolan.ppro >you write:
  > | Use "gcc --print-search-dirs" to get a list of its internal search paths.
  > 
  > Interesting, didn't know about that one :)...
Don't feel bad -- I worked on the compiler for years before I new about
it.

  > The order seems pretty messy though, it looks often in
  > directories that do not exist (but carry the version
  > of THIS particular snapshot/version).
We can't even guess what might be going on since we don't know how
you configured the toolchain.

Many directories are searched because they *may* contain things
built by other packages like binutils, libg++, etc.  Just because
a directory is empty in an egcs installation doesn't mean it's
always empty.

Some paths come from compiler builtins derived from MD_EXEC_PREFIX
(which is necessary to find some system things like crt0), others
are derived from your configure arguments).  Depending on the exact
values, some searches of the same directory would be considered
normal.

  > Me thinks that the search paths do need a face lift.
Maybe.  I think you're taking an overly simplistic viewpoint of
how they're used.

jeff