From owner-freebsd-ports@freebsd.org Wed Mar 23 11:10:16 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60E4AADA905 for ; Wed, 23 Mar 2016 11:10:16 +0000 (UTC) (envelope-from freebsd-ports@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 934A41847 for ; Wed, 23 Mar 2016 11:10:15 +0000 (UTC) (envelope-from freebsd-ports@m.gmane.org) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1aigfs-0008PQ-Hc for freebsd-ports@freebsd.org; Wed, 23 Mar 2016 12:10:04 +0100 Received: from p5099ba30.dip0.t-ipconnect.de ([80.153.186.48]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 Mar 2016 12:10:04 +0100 Received: from christian.baer by p5099ba30.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 Mar 2016 12:10:04 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-ports@freebsd.org From: Christian Baer Subject: Re: Is the kmymoney port broken? Date: Wed, 23 Mar 2016 11:05:35 +0100 Lines: 61 Message-ID: References: <3819213.lvxybsyZCo@falbala> <86io0eygi4.fsf@FreeBSD.org> <56F154BF.3020209@uni-dortmund.de> <86a8lqy49r.fsf@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: p5099ba30.dip0.t-ipconnect.de User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 In-Reply-To: <86a8lqy49r.fsf@FreeBSD.org> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2016 11:10:16 -0000 On 03/22/16 15:29, Raphael Kubo da Costa wrote: > CC'ing the list again. Sorry about that. I'm reading this list via gmane and I pushed the wrong button. :-) > It's easy to check: pkg info kdelibs. The version field should say > 4.14.3_6. If you've just built kmymoney I'd assume it would require that > new version though. Please also make sure your Mk/bsd.kde4.mk is at > r411201 or later. Oh, you were also talking about the version number. God, I really must have had a bad day with next to no brain activity yesterday! Anyways... I rebuilt the kdelibs from the ports and did a make reinstall. After that I rebuilt KMymoney and the install worked fine. Thanks for your help! > Yes, I am referring to this commit I made a week ago: > > > Which made kdelibs (and several ports that depend on it) install its > headers into /usr/local/include/kde4 instead of /usr/local/include. The reason I was a little skeptical about this at first is because I tried building KMymoney from souce a couple of months ago too. It didn't work either (actually stopped at the same point). The reason I didn't pursue the issue any further at the time was because a truckload of work was thrown my way shortly after I ran into this and thus put installing and using KMymoney on hold for a while, since this was more a personal thing for me. Now is the second time around I ran into the same problem, so I wasn't sure if a really recent change could have been the issue. > You can try recompiling x11/kdelibs4 after making sure both the port and > bsd.kde4.mk are at their latest versions, but I think it should have > already happened when you tried building kmymoney. Pretty sure you are right about this considering I completely rebuild the entire ports tree directly before this. > A few other things you can try in order to rule out other possibilities: > - After building kmymoney, run `find work -name importinterface.h' to > check where the header was staged. > - See if resetting your build options (make rmconfig) makes any > difference. I'll make a note of this, but since I got it to work just by rebuilding the kdelibs, I didn't try any of these things this time round. :-) > It would also be helpful if you could attach your whole build log if the > problem persists. It didn't persist, so thanks again for your help! I really appreciate you taking the time for this! Kind regards, Chris