Date: Wed, 24 Jan 2007 18:47:53 -0500 From: Mikhail Teterin <mi+kde@aldan.algebra.com> To: Kris Kennaway <kris@obsecurity.org> Cc: cvs-ports@freebsd.org, ports-committers@freebsd.org Subject: Re: tcltls hanging in self-tests? (Re: cvs commit: ports/devel/tcllib Makefile) Message-ID: <200701241847.53537@aldan> In-Reply-To: <20070124214042.GA39398@xor.obsecurity.org> References: <200701231143.l0NBhSRF010390@repoman.freebsd.org> <200701241635.47510@aldan> <20070124214042.GA39398@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 24 January 2007 16:40, Kris Kennaway wrote: = > This is the first time I hear about the problem -- there is nothing = > unusual or unreasonable about asking the problem-reporter for the = > stdout/stderr, is there? = = No, but you have to also accept that I can't oblige, as previously stated. Indeed: = > Can I see the build-log, please? Which test is hanging? = I don't know, I haven't had the time to debug it (the build log does = not exist since it does not complete). I accept that, and shall wait until you find the time to collect the output. A semi-educated guess: the problem may have to do with the build-machine dropping (rather than nacking) attempts to connect to a closed port. Is pointyhat (mis)configured this way? Yours, -mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200701241847.53537>