Date: Mon, 17 Jan 2005 22:06:41 +0100 From: Kirill Ponomarew <krion@voodoo.oberon.net> To: Tom Huppi <thuppi@huppi.com> Cc: freebsd-ports@freebsd.org Subject: Re: Qt33 Build Problem Message-ID: <20050117210641.GB2505@voodoo.oberon.net> In-Reply-To: <Pine.BSF.4.58.0501171457370.32657@nuumen.pair.com> References: <BB7A3D4475F89F4696DC91D40AA5F38F026F5998@mailbox.Hunter.com> <20050117153341.GO93155@voodoo.oberon.net> <Pine.BSF.4.58.0501171457370.32657@nuumen.pair.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 17, 2005 at 03:23:36PM -0500, Tom Huppi wrote: > There is a reference to it in the 5.3 Errata (at least): > > http://www.freebsd.org/releases/5.3R/errata.html > > ...but I would have had a bit more trouble finding it had I not > known to look for the string 'libc_r'. > > I worked at re-building Qt33 for quite some time, but > 'libqt-mt.so' still retains a reference to 'libc_r'. If there are > any common reasons why this may be, I'de be interested to know of > them. I got rid of all other references (except one other library > associated also with Qt33), but couldn't nuke that one so I > resorted to the 'libmap.conf' hack which I would have preferred > not to do. In most cases there are dependencies which are still linked to libc_r, so check them first. -Kirill
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050117210641.GB2505>