------- Comment #3 from tromey at gcc dot gnu dot org 2007-05-22 19:11 -------
My recollection is that the special -I behavior is there because
the system headers have special non-warning properties.
This situation doesn't apply to -L.
> 2. Software is often compiled with configure, make, make install. How can one
> force the compiler to look in /usr/include & /usr/lib first (i.e. override the
> user's environment)?
Generally speaking this is not a good idea. Usually people *want* their
environment to influence configure, and usually if configure overrides this
it means difficult to fix problems on weirder systems.
I am leaving this open considering that there is still a documentation bug
to be fixed here.
--
tromey at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at gcc dot gnu dot
| |org
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2007-05-22 19:11:27
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31186
