Matthew Pounsett wrote:
>
> On 08-Jul-2008, at 16:56 , Martin Costabel wrote:
>
>> Must be something on your machine or network. On 2 10.5.4 systems I
>> get the output you say is correct, namely more or less the same as
>> this one:
>
> Okay, thanks to the people that responded. It looks lik
Hi,
ahh, as i thought, it's the problem with bind8 and bind9.
Well, you already build it with -DBIND_8_COMPAT but that will break it.
Just remove this flag and include /usr/include/nameser8_compat.h
in the dns.c and mtr will work as it should.
BTW, dig works here.
Regards
Andreas
On Jul 8, 200
On 08-Jul-2008, at 16:56 , Martin Costabel wrote:
Must be something on your machine or network. On 2 10.5.4 systems I
get the output you say is correct, namely more or less the same as
this one:
Okay, thanks to the people that responded. It looks like the two
things are unrelated after
Matthew Pounsett wrote:
> Possibly related... on my systems where mtr cannot do forward lookups,
> the +trace option to the default install of 'dig' also appears broken.
> Can anyone else confirm that this is broken on their 10.5.4 machines
> and/or working on 10.4? If anyone can confirm this
On Tuesday 08 July 2008 16:28:04 Matthew Pounsett wrote:
> On 19-Jun-2008, at 16:03 , Andreas Gockel (gecko2) wrote:
> > On Jun 19, 2008, at 18:47 , Charles Lepple wrote:
> >> otool -L /sw/bin/mtr
> >
> > /sw/bin/mtr:
> > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
> > vers
On 19-Jun-2008, at 16:03 , Andreas Gockel (gecko2) wrote:
On Jun 19, 2008, at 18:47 , Charles Lepple wrote:
otool -L /sw/bin/mtr
/sw/bin/mtr:
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 111.1.1)
/sw/lib/ncurses/libncurses.5.dylib (compatibility version 5.0
