From owner-freebsd-ports Wed Apr 26 13:50: 5 2000 Delivered-To: freebsd-ports@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id C328C37BADC for ; Wed, 26 Apr 2000 13:50:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id NAA83228; Wed, 26 Apr 2000 13:50:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Wed, 26 Apr 2000 13:50:02 -0700 (PDT) Message-Id: <200004262050.NAA83228@freefall.freebsd.org> To: freebsd-ports@FreeBSD.org Cc: From: Chris Piazza Subject: Re: ports/17938: KDM dumping core in 4.0-STABLE (!) Reply-To: Chris Piazza Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR ports/17938; it has been noted by GNATS. From: Chris Piazza To: "Jeffrey S. Sharp" Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: ports/17938: KDM dumping core in 4.0-STABLE (!) Date: Wed, 26 Apr 2000 13:42:15 -0700 On Mon, Apr 17, 2000 at 03:00:03PM -0700, Jeffrey S. Sharp wrote: > The following reply was made to PR ports/17938; it has been noted by GNATS. > The following is a possible workaround for ports/17938. It worked for me > and at least one other person who was experiencing this > problem. Basically, all one needs to to is recompile KDM without > optimization: > > I hope this helps to narrow down where the problem is. Worked for me. I'm going to add a patch to the port to put -O0 after CFLAGS/CXXFLAGS in kdm/Makefile which should fix this problem. You can add this patch below as ports/x11/kdebase/patches/patch-az or just cvsup in a little while. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message