BIND 10 #1644: system include header ordering needs

BIND 10 Development do-not-reply at isc.org
Thu Feb 2 03:03:04 UTC 2012


#1644: system include header ordering needs
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  major         |                    Milestone:  New
           Component:  Unclassified  |  Tasks
           Sensitive:  0             |                     Keywords:
         Sub-Project:  Core          |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 Some systems header's don't include their needed headers. So you can get
 errors like:

 {{{

 /usr/include/netinet/in.h:141: error: 'in_addr_t' does not name a type

 ...

 /usr/include/netinet6/in6.h:118: error: 'u_int8_t' does not name a type

 ...

 ../../../ext/asio/asio/detail/impl/socket_ops.ipp:93: error: 'msg_namelen'
 is not a member of 'msghdr'

 ...

 ../../../ext/asio/asio/ip/impl/address_v6.ipp:193: error: 'const union
 in6_addr::<anonymous>' has no member named '__u6_addr8'


 }}}

 (maybe thousands of errors)

 The fixes are trivial but I am making a branch to test first on various
 systems.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1644>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list