BIND 10 #3213: BIND 10 doesn't compile/work on Mac OS X 10.9

[BIND 10 Development]

#3213: BIND 10 doesn't compile/work on Mac OS X 10.9
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  defect        |  jinmei
            Priority:  medium        |                       Status:
           Component:  build system  |  reviewing
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20131015
         Sub-Project:  Core          |                   Resolution:
Estimated Difficulty:  0             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by muks):

 * owner:  muks => jinmei


Comment:

 Hi Jinmei

 It's good to see you still compiling BIND 10 and also
 contributing patches. :)

 Here is my review of this branch. Will you make these changes (if you
 agree) to the branch or do we have to make them?

 * There is a compile issue on Fedora 19 with the GCC 4.8.2 compiler:
 {{{
 data.cc: In function 'int isc::data::{anonymous}::skipTo(std::istream&,
 const string&, int&, int&, const char*, const char*)':
 data.cc:307:1: error: control reaches end of non-void function [-Werror
 =return-type]
 }}}

 * There were clang++ fixes that were merged to `master` branch recently
   (to make it compile with clang++ 3.3 rc3 on Fedora 19). Please can you
   rebase this branch on `master`? The
   `-Wno-tautological-constant-out-of-range-compare` may be unnecessary.

 * In the `pthread_cond_destroy()` patch, it is testing using
   `/usr/bin/sw_vers` for a specific version. A long time ago, when
   working on a different ticket, I think you had advised me (maybe when
   working on a Solaris issue) that it is better to test for
   features/bugs directly and set configure variables based on those,
   instead of any system specific tools or versions. Would it make sense
   to test whether `EBUSY` is returned in this case or not?

-- 
Ticket URL: <http://bind10.isc.org/ticket/3213#comment:4>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development