Re: "changing search order" warning with libiconv 1.8 (GCC 3.1, Solaris 8)

[Bruno Haible]

Paul Eggert writes:

> > The warning is documented in the gcc documentation,
> 
> Yes, but the warning isn't appropriate here.

I agree. Your /opt/reb/include is not the same as /usr/include,
therefore gcc's private include directory hierarchy does not contain
modified copies of /opt/reb/include/*, and therefore there is no
reason to warn about -I/opt/reb/include.

> Users should be able to use the same prefix for all the programs they
> install.  We shouldn't insist that different GNU programs must use
> different prefixes in order to work properly.

Agreed.

Can you submit a gcc bug for it?

> But it is a common GCC bug on Solaris, as it occurs with the latest
> GCC and Solaris versions.  It should be easy enough for iconv.m4 to
> work around the GCC bug.

If you report it, the bug is likely to go away in gcc 3.2.

I don't think it is easy for iconv.m4 to work around the
warning, because for an arbitrary gcc installation, only gcc knows
which directories are in its default search path. Too many things can
go wrong if -I/opt/reb/include is omitted but -L/opt/reb/lib is added.

Bruno