jerry at seibercom.net
Thu Feb 23 00:31:11 UTC 2012
On Thu, 23 Feb 2012 01:54:53 +0200
Andriy Gapon articulated:
> on 23/02/2012 01:00 Andriy Gapon said the following:
> > on 23/02/2012 00:48 Alberto Villa said the following:
> >> On Wednesday 22 February 2012 23:28:01 Jerry wrote:
> >>> Has anyone else had a problem updating the "net-im/telepathy-qt4"
> >>> port? It has failed to build twice for me in the past 12 hours.
> >> It looks like you have some problems with Qt 4 ports, qmake and
> >> qt4-corelib mostly. Can you try rebuilding them?
> >> By the way, out of curiosity... what do you need Telepathy-Qt for?
> > Just in case, I've run into the same problem.
> > Couple of points (in a simple-user mode):
> > - my Qt installation should be "good" as no other port had any
> > problem with it and there were no run-time issues and the relevant
> > Qt ports were installed a long time ago
> > - I don't "need" that port for anything (in fact I don't even know
> > what it provides) - it must be (or have been) a dependency of
> > something
> > A more educated observation: it seems that telepathy-qt4 is not
> > required by any other installed package now.
> OK, in my case the problem was caused by qmake-3.3.8_1 being
> installed (again, for some unknown reason, no other package depending
> on it). FindQt.cmake was confused by 'qmake' executable from
> qmake-3. Once it was deinstalled, telepathy-qt4 build worked fine.
Same here. I had "qmake-3.3.8_1" installed, reason unknown also. I did
a pkg_delete of the port and then attempted to build the
"telepathy-qt4" port. It went flawlessly. Problem "apparently" solved.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
More information about the freebsd-ports