From owner-freebsd-questions@FreeBSD.ORG Sat Mar 1 10:42:56 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E6DF3FE2 for ; Sat, 1 Mar 2014 10:42:55 +0000 (UTC) Received: from alogt.com (alogt.com [69.36.191.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B9C2E185A for ; Sat, 1 Mar 2014 10:42:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=nqKqPrVSQoBsRyzbOA/cfkYdD2ooj4Cm9sH7M4wd/4w=; b=I7PXZYRqOt1NNFjuRtct0weP4UwmtkMMi6LKy9TXA7tlgPVWhS3GXO8LXJ8qrZOiq3tJi1jQKaqLlreX73ZlaJW5jyKo31NmVuxaEu94fIsgaVT4YA3Ta//s4nKDtBBT7ytBT+Nn45Z8uftoLP01eRXYE2VcF4yfVY3ecjARlLo=; Received: from [39.197.53.239] (port=30249 helo=X220.alogt.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from ) id 1WJhNd-003K4l-Bw; Sat, 01 Mar 2014 03:42:54 -0700 Date: Sat, 1 Mar 2014 18:42:40 +0800 From: Erich Dollansky To: jerry@seibercom.net Subject: Re: Unable to build kde-workspace Message-ID: <20140301184240.6d448e33@X220.alogt.com> In-Reply-To: <017401cf3539$97c6cd30$c7546790$@seibercom.net> References: <00b801cf349b$a3801850$ea8048f0$@seibercom.net> <20140301000529.6a50fdec@X220.alogt.com> <011501cf34b2$ad71c090$085541b0$@seibercom.net> <20140301083551.29b44368@X220.alogt.com> <017401cf3539$97c6cd30$c7546790$@seibercom.net> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd10.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Mar 2014 10:42:56 -0000 Hi, On Sat, 1 Mar 2014 05:32:48 -0500 "Jerry" wrote: > > On Friday, February 28, 2014 7:36 PM Erich Dollansky wrote: > > > > Hi, > > > > On Fri, 28 Feb 2014 13:27:02 -0500 > > "Jerry" wrote: > > > > > > > Due to this problem, I am halfway through updating KDE4. > > > > > Unfortunately, now I cannot even start KDE, so I have a > > > > > serious problem. > > > > > > > > > > > > > you can avoid this problem in the future by using a tool like > > > > portupgrade > > > and > > > > by installing simple window manager like blackbox. > > > > > > > > Even if your KDE would be gone, you still would be able to use > > > > X. > > > > > > I used "portmaster" although I usually use "portupgrade". Building > > > manually though does not fix the problem. > > > > > I know. Just stay with portupgrade for the future. Always create > > packages > as > > a backup. So, you can always go back to the old version, no matter > > what happens. > > > > I would suggest that you try an older revision now. I was able to > > build > KDE > > with revision 342933. There should be newer revisions with which it > > still > will > > work. > > I have discovered that this is a known problem. There are at least two > solutions. > > 1) Set "GLES=off: OpenGL ES 2.0 support in kwin and kinfocenter" in > the "/x11/kde4-workspace" port. > > 2) Run: "pkg remove -f libglesv2-9.1.7" before building the port. > > Evidently this problem does not surface on a fresh installation of > KDE4, It would have been nice if there had been a notation in the > UPDATING log that this condition existed. > this is interesting. I have KDE always installed because I use some of its programs but not KDE itself. As such, I have to upgrade it all the while. So, I am just lucky that either GLES is off by chance or something else helped me. Yes, a note in UPDATING would be needed in cases like this. Erich