Date: Wed, 24 Jan 2007 16:35:46 -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: <200701241635.47510@aldan> In-Reply-To: <20070124212856.GA39189@xor.obsecurity.org> References: <200701231143.l0NBhSRF010390@repoman.freebsd.org> <200701241624.05672@aldan> <20070124212856.GA39189@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 24 January 2007 16:28, Kris Kennaway wrote: = On Wed, Jan 24, 2007 at 04:24:05PM -0500, Mikhail Teterin wrote: = > On Wednesday 24 January 2007 16:03, Kris Kennaway wrote: = > = > Tcltls is a different port... Are you sure, tcllib is the problem? = > = = > = Sorry, I crossed wires, I'm referring to tcltls here. = > = > I don't remember hearing about a problem with tcltls' self-tests -- = > neither from you nor from regular users... I would need a build-log... = = See up-thread and the bits you snipped. Yes, I saw your note, that you weren't able to obtain a log yet, but I need it anyway. 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? Yours, -mi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200701241635.47510>