Re: tai64n date format

["Vahid Moghaddasi" <vahid.moghaddasi@gmail.com>]

On 4/1/07, Charles Cazabon <qmail@discworld.dyndns.org> wrote:
> Yes.  You can either patch matchup so it can read those tai64n timestamps
> (Google for patches), or convert them -- Google for "tai64n2tai" or a similar
> program.
I have a copy of the patched matchup but never used it since it
reports a much longer delay than the non patched one. cat current|
matchup-patched | zoverall
Total ddelay (s): 278639.381440
Average ddelay per success (s): 29.407850
Total xdelay (s): 70794.147946

Non-patched matchup shows 0.00 for all delay. Not sure which one is correct.

I spent a long time to get tai64n2tai compiled on Solaris but no luck
I guess they write these tools for Linux only, keep getting strange
errors:
Linking ./src/* into ./compile...
Compiling everything in ./compile...
./compile tai64n2tai.c
tai64n2tai.c: In function `main':
tai64n2tai.c:26: error: `tai' undeclared (first use in this function)
tai64n2tai.c:26: error: (Each undeclared identifier is reported only once
tai64n2tai.c:26: error: for each function it appears in.)
tai64n2tai.c:26: error: `t' undeclared (first use in this function)
tai64n2tai.c:26: warning: implicit declaration of function `tai64n_decode'
tai64n2tai.c:29: warning: implicit declaration of function `tai_encode'
*** Error code 1
make: Fatal error: Command failed for target `tai64n2tai.o'