From owner-freebsd-ports@FreeBSD.ORG Thu Feb 28 17:18:33 2013 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1DE8D4D1 for ; Thu, 28 Feb 2013 17:18:33 +0000 (UTC) (envelope-from eischen@vigrid.com) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id DA53F331 for ; Thu, 28 Feb 2013 17:18:32 +0000 (UTC) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.6/8.14.6/NETPLEX) with ESMTP id r1SHIVxT045911 for ; Thu, 28 Feb 2013 12:18:31 -0500 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.4.1 (mail.netplex.net [204.213.176.10]); Thu, 28 Feb 2013 12:18:31 -0500 (EST) Date: Thu, 28 Feb 2013 12:18:31 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: ports@FreeBSD.org Subject: Re: net-im/kopete-kde4 broken on -current, stops kdenetwork build In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2013 17:18:33 -0000 On Thu, 28 Feb 2013, Daniel Eischen wrote: > I'm trying to upgrade my ports on -current: > > FreeBSD rigel 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r247154: Fri Feb 22 > 14:59:28 EST 2013 deischen@rigel:/usr/obj/opt/FreeBSD/current/src/sys/rigel > amd64 > > And hitting this error in building net-im/kopete-kde4: [ ... ] > And it goes on with more errors for Q_CORE_EXPORT, QT_END_NAMESPACE, > QT_END_HEADER. Full log here: > > http://people.freebsd.org/~deischen/ports/kdenetwork.log > > My qt4 is up to date at 4.8.4. qnamespace.h includes qglobal.h, > which defines these macros, so I'm not sure how they are not > being defined. I'm not sure why, but there were stale include files for qt-3.3.8_14 which were not deinstalled, and these were being picked up over the qt4 includes. -- DE