--- Comment #15 from rguenth at gcc dot gnu dot org 2008-01-25 20:32
---
Closing as of comment #12; the issue can be worked around by re-shuffling
include
paths to put those that work first.
--
rguenth at gcc dot gnu dot org changed:
What|Removed
--- Comment #14 from ed at catmur dot co dot uk 2007-11-14 21:16 ---
(In reply to comment #13)
I don't see why this is different from the case where the header file cannot
be
opened.
It isn't, I guess - is there a bug about that?
And in that case, as Tom says, it seems like there
--- Comment #13 from manu at gcc dot gnu dot org 2007-11-14 02:02 ---
Ed,
I don't see why this is different from the case where the header file cannot be
opened. And in that case, as Tom says, it seems like there is some problem with
the filesystem setup that the user should be aware
--- Comment #12 from tromey at gcc dot gnu dot org 2007-01-21 03:23 ---
One odd thing here is that if -Werror is given, then an inaccessible
directory will cause a compilation failure.
I would prefer we not check this patch in. I don't think there is
any obviously correct behavior on
--- Comment #11 from ed at catmur dot co dot uk 2005-11-29 23:55 ---
This is not invalid. Yes, reiser4 is broken, but so is gcc.
gcc (3.4.4, I haven't used 4.x yet) dies when it encounters an inaccessible
directory as a subdirectory of a member of the include path. See comment 6.
--
