Re: Distributional bug? config.h should not be installed

[Shai Ayal]

On 2/20/06, John W. Eaton <address@hidden> wrote:
> On 18-Feb-2006, Sebastien Loisel wrote:
>
> | address@hidden octave-gui]$ locate octave |grep config
> | /usr/include/octave-2.1.57/octave/config.h
> |
> | I'm pretty sure you're not supposed to install config.h. The reason is that
> | all autoconfiscated packages have a config.h, and they all define the same
> | symbols but with different values, so there's a high chance of symbol
> | clashes. Right now I'm unable to use my own config.h without the compiler
> | complaining.
>
> Yes, fixing this has been on my list for a long time.  I don't see it
> as urgent however, because you can use
>
>  #include <octave/config.h>
>
> in Octave code, and only add -I/usr/include/octave-VERSION to the
> compiler flags.  Doesn't that allow you to avoid most conflicts?  Or
> is the problem that you hit errors (or at least many warnings) due to
> redefining preprocessor symbols if you include Octave's config.h and
> your own?

This is also a problem in octplot where in one oct file I include
"oct.h" and than octplot's config.h -- I get warnings for redefined
symbols. This is not so bad because the symbols are redefined to the
values I need

Shai