From owner-freebsd-ports Mon Feb 5 16:49: 8 2001 Delivered-To: freebsd-ports@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 2420737B491 for ; Mon, 5 Feb 2001 16:48:49 -0800 (PST) Received: from v-ger.we.lc.ehu.es (lxpx174.lx.ehu.es [158.227.26.74]) by polaris.we.lc.ehu.es (8.11.1/8.11.1) with ESMTP id f160mjb03081 for ; Tue, 6 Feb 2001 01:48:45 +0100 (MET) Received: from we.lc.ehu.es (localhost [127.0.0.1]) by v-ger.we.lc.ehu.es (8.11.1/8.11.1) with ESMTP id f160kSk01296 for ; Tue, 6 Feb 2001 01:46:28 +0100 (CET) (envelope-from jose@we.lc.ehu.es) Message-ID: <3A7F4964.6422FF5C@we.lc.ehu.es> Date: Tue, 06 Feb 2001 01:46:28 +0100 From: "Jose M. Alcaide" Organization: Universidad del Pais Vasco - Dpto. de Electricidad y Electronica X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: ports@FreeBSD.org Subject: SIGSEGV while installing kdebase2 port? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I am trying to build KDE 2.0.1 on a system running a pretty recent FreeBSD 5.0-CURRENT (two days old). I wiped out all installed packages, except XFree86-3.3.6_4, and also updated the ports tree before beginning the KDE build. However, I am getting a SIGSEGV while installing kdebase2: ..... Installing non-KDE applications pwd=`pwd`; \ (cd . && $pwd/kappfinder_install "/usr/local/share/applnk") Creating link /root/.kde/socket-defiant.we.lc.ehu.es. Created link from "/root/.kde/socket-defiant.we.lc.ehu.es" to "/tmp/ksocket-root" Segmentation fault - core dumped gmake[3]: *** [runkappfinder_yes] Error 139 ..... Indeed, kappfinder_install dumps core every time. I tried to recompile it without any "-On" options to no avail. Then, I used gdb and this is what I found: Program received signal SIGSEGV, Segmentation fault. 0x28475f1b in QCString::resize () from /usr/X11R6/lib/libqt2.so Could this be a problem with qt-2.2.4? I built KDE 2.0 about two months ago with no problems, but then qt-2.2.3 was used. Is anybody experiencing the same problem? I didn't find any reference to it in the archives. Cheers, -- JMA ****** Jose M. Alcaide // jose@we.lc.ehu.es // jmas@FreeBSD.org ****** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message