> If you keep header files with names like `random.h' in the libguile
> directory, you would need to be certain that `-I.' was never used
> while compiling anything in that directory. You would likewise need
> to be certain that `-Ilibguile' was never used in the top directory
> and `-I../libguile' was never used in any sibling-directories of
> libguile. All that may break other things, or it may not. The
> problem is that it's a "brittle solution", meaning that it may solve
> this problem, but a similar problem may pop up again later.
Well, any solution requires discipline. You're suggesting that every
header file Guile uses, internal and external, should be named so as
to be globally unique, distinguished from every header file on every
machine Guile might be installed on. Not impossible, but also
somewhat brittle, given the number of header files involved.
I think Mikael's solution is the correct one. It's a bug to use -I to
add a directory to the #include search path that contains header files
named in an "unsanitary" way.
