Assignment

const char **p;
      char **q; 

p=q;

causes message 'assignment from incompatible pointer type', 
which is wrong.

While it is true that because of ANSI C Standard error blindly
ANSI compatible compiler should claim these pointers incompatible,

1.well known compilers (Borland, Watcom) even in full ANSI compatibility
mode allow themselves to correct standard here and do not issue warning,

2.GCC is not bound to repeat ANSI errors at all, because it claims ANSI C
too restrictive.

The problem, as far as a potentially superfluous warning can
be called a problem, is with gcc, and not in any way specific
to DJGPP. I have convinced the poster to relay this problem to
gnu.gcc.bug.

Original poster got told by the gcc developers that this
is not a bug, i.e. the warning is for real.