Re: named problem (evbarm)

[jnemeth%victoria.tc.ca@localhost (John Nemeth)]

On May 24,  3:45pm, Jukka Marin wrote:
} On Tue, Jan 01, 2008 at 05:01:55PM +0000, Julian Coleman wrote:
} > 
} > > I have a NetBSD 4.0 system (evbarm) which works pretty well except for
} > > named.
} > 
} > I wonder if it's a libpthread problem.  Could you add evbarm to the list
} > of "no pthread" architectures in src/usr.sbin/bind/Makefile.inc and
} > rebuild named?
} 
} First, I hope you don't mind me Cc:ing to netbsd-users.
} 
} I changed it to this:
} 
} .if (${MACHINE_ARCH} == "sparc" || ${MACHINE_ARCH} == "sparc64" \
}         || ${MACHINE_ARCH} == "mipsel" || ${MACHINE_ARCH} == "mipseb" \
}         || ${MACHINE_ARCH} == "evbarm" )

     "evbarm" is most likely a ${MACHINE}, not a ${MACHINE_ARCH}.  You
probably want $MACHINE_ARCH} == "arm".

} NAMED_USE_PTHREADS?=no
} .else
} NAMED_USE_PTHREADS?=yes
} .endif
} 
} but named was still built with libpthread.  Then I added
} 
} NAMED_USE_PTHREADS=no
} 
} and now named no longer uses libpthread - and yes, it works now (as far
} as I know).
} 
} Are there other binaries that might suffer from the same problem under
} evbarm?  Maybe libpthread should be disabled for other binaries as well?

     Off the top of my head, I don't think there are any other apps in
base that use libpthread.

}-- End of excerpt from Jukka Marin