> Paul (or Arthur) - any reason you can think of that zdump.c should not
> include private.h?

A comment from the top of zdump.c:

    /*
    ** This code has been made independent of the rest of the time
    ** conversion package to increase confidence in the verification it provides.
    ** You can use this code to help in verifying other implementations.
    */

        --ado


On Thu, Jan 31, 2013 at 10:04 AM, Robert Elz <kre@munnari.oz.au> wrote:
    Date:        Thu, 31 Jan 2013 06:36:22 +0700
    From:        Robert Elz <kre@munnari.oz.au>
    Message-ID:  <6086.1359588982@eos.noi.kre.to>

  | If you got the binary as part of some system or other, then you need to
  | ask the system builders why they chose to exclude it.

It turns out that the most likely cause of this, is that zdump.c
does not #include "private.h", and that (at least on some systems)
private.h is where the relevant #defines tend to be placed (rather than
in CFLAGS in the Makefile).

Paul (or Arthur) - any reason you can think of that zdump.c should not
include private.h?

kre