Hello Francis,

> Two questions about the second (and blocking) problem:
>   1- can you return here the value of FLEXIBLE_ARRAY_MEMBER
>    from config.h? (it should be set to 1 for an old compiler,
>    to nothing for a C 99 compiler)

trinity3:/usr/src/archive/dns/bind-9.11.2-P1$ grep FLEXIBLE_ARRAY_MEMBER 
config.h
    d[FLEXIBLE_ARRAY_MEMBER]; };', the struct hack can be used with pre-C99
#define FLEXIBLE_ARRAY_MEMBER 1




>   2- replace in lib/isc/ht.c the [] after key by
>    [FLEXIBLE_ARRAY_MEMBER].

Ah.. I think you meant:
--
trinity3:/usr/src/archive/dns/bind-9.11.2-P1# diff -u lib/isc/ht.c.orig 
lib/isc/ht.c
--- lib/isc/ht.c.orig   Wed Jan 17 11:46:12 2018
+++ lib/isc/ht.c        Wed Jan 17 11:46:23 2018
@@ -28,7 +28,7 @@
         void *value;
         isc_ht_node_t *next;
         size_t keysize;
-       unsigned char key[];
+       unsigned char key[FLEXIBLE_ARRAY_MEMBER];
  };

  struct isc_ht {
--


> It should compile with this (if there is no other problem).

Looks like this change worked and it completed building. Interestingly 
enough, this lib/isc/ht.c file doesn't exist in the 9.11.2-P1 sources.


> I am still interested by your compiler version.
> According to Gnu docs the deprecated attribute is
> supported by gcc 3.1.1 and perhaps older (I found
> only 3.0.4 and 2.95.3 docs, both without this atttribute).

Per my previous email, this machine is running 2.95.
--
trinity3:/usr/src/archive/dns/bind-9.10.6-P1# gcc -v
Reading specs from /usr/lib/gcc-lib/i586-mandrake-linux/2.95.2/specs
gcc version 2.95.2 19991024 (release)
--


So.. with your help, we've found a solution but I'm curious how we 
proceed here.  Do you feel there is any issue with rolling out this new 
binary (I doubt it)?  How does ISC roll out build fixes for critical 
security releases?  Will they release a 9.11.2-P2 ASAP? Maybe you just 
offer patches to help impacted users until you publish a new 9.11.x 
release?
Just curious.

--David