From owner-freebsd-questions Tue Dec 4 12: 8:24 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mcqueen.wolfsburg.de (pns.wobline.de [212.68.68.5]) by hub.freebsd.org (Postfix) with ESMTP id F22FE37B41B for ; Tue, 4 Dec 2001 12:08:13 -0800 (PST) Received: from colt.ncptiddische.net (ppp-338.wobline.de [212.68.71.59]) by mcqueen.wolfsburg.de (8.11.3/8.11.3/tw-20010821) with ESMTP id fB4K7tA11401; Tue, 4 Dec 2001 21:07:55 +0100 Received: from poison.ncptiddische.net (poison.ncptiddische.net [192.168.0.5]) by colt.ncptiddische.net (8.11.6/8.11.6) with ESMTP id fB4K8vW07924; Tue, 4 Dec 2001 21:08:58 +0100 (CET) (envelope-from nils@tisys.org) Received: from poison.ncptiddische.net (poison.ncptiddische.net [192.168.0.5]) by poison.ncptiddische.net (8.11.6/8.11.6) with ESMTP id fB4K7Kb97189; Tue, 4 Dec 2001 21:07:55 +0100 (CET) (envelope-from nils@tisys.org) Date: Tue, 4 Dec 2001 21:07:20 +0100 (CET) From: Nils Holland To: Kenneth Wayne Culver Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Problem with new KDE 2.2.2 port? In-Reply-To: Message-ID: <20011204210238.B97165-100000@poison.ncptiddische.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 4 Dec 2001, Kenneth Wayne Culver wrote: > I've had this problem, and other (possibly unrelated) problems trying to > compile the latest port of kde 2.2.2. > > I don't think kdemultimedia or koffice compile either. > > In addition, gcc keeps giving me "Internal Compiler errors" when > compiling, but if I just restart the build, everything continues fine for > a while. KDE2 is the only port that has this problem, and I can > successfully build a kernel and world too, so I'm not sure what the > problem is. This is on -CURRENT as of a week and a half ago. My problems appear on -STABLE as of last Saturday. I don't seem to get any "Internal Compiler Errors" here on -STABLE, but nice to hear that I'm not the only one having problems ;-) I haven't yet tried to do anything about these problems myself, but I'll probably change that and actually look at it. BTW: "objprelink" has just been fixed according to a commit message I read. Strange - it seemed to work here this morning, at least I don't think that a problem with objprelink has anything to do with the problems we are experiencing. Greetings Nils Nils Holland Ti Systems - FreeBSD in Tiddische, Germany http://www.tisys.org * nils@tisys.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message