From owner-freebsd-questions@FreeBSD.ORG Fri Dec 30 19:43:42 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C0BE16A41F for ; Fri, 30 Dec 2005 19:43:42 +0000 (GMT) (envelope-from gerard@seibercom.net) Received: from smtp3.suscom.net (smtp3.suscom.net [64.78.119.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8798143D60 for ; Fri, 30 Dec 2005 19:43:40 +0000 (GMT) (envelope-from gerard@seibercom.net) Received: from localhost (unknown [127.0.0.1]) by smtp3.suscom.net (Postfix) with ESMTP id 6007B210131 for ; Fri, 30 Dec 2005 14:43:38 -0500 (EST) Received: from smtp3.suscom.net ([127.0.0.1]) by localhost (smtp3.suscom.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 11018-01-18 for ; Fri, 30 Dec 2005 14:43:27 -0500 (EST) Received: from seibercom.net (ip148.217.susc.suscom.net [216.45.217.148]) by smtp3.suscom.net (Postfix) with SMTP id 1F780210138 for ; Fri, 30 Dec 2005 14:43:27 -0500 (EST) Received: from [192.168.0.2] (//gerard [192.168.0.2]) by seibercom.net (8.13.4/8.13.4) with ESMTP id jBUJhRx7013364 for ; Fri, 30 Dec 2005 14:43:27 -0500 (EST) (envelope-from gerard@seibercom.net) Date: Fri, 30 Dec 2005 14:43:30 -0500 From: Gerard Seibert To: freebsd-questions@freebsd.org Sender: gerard@seibercom.net Organization: Seibercom X-Face: "\j?x](l|]4p?-1Bf@!wN<&p=$.}^k-HgL}cJKbQZ3r#Ar]\%U(#6}'?<3s7%(%(gxJxxcR nSNPNr*/^~StawWU9KDJ-CT0k$f#@t2^K&BS_f|?ZV/.7Q Message-Id: <20051230144037.836A.GERARD@seibercom.net> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Mailer: Becky! ver. 2.24.01 [en] X-Virus-Scanned: amavisd-new at suscom.net Subject: Unable to build 'icu-3.4' X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Dec 2005 19:43:42 -0000 Several users, including myself, are unable to install 'icu-3.4'. I have contacted both the maintainer and the 'icu' development staff regarding this problem. The following is the feed back that I have received up to this point. First of all, the output from 'uname -a' FreeBSD seibercom.net 5.4-STABLE FreeBSD 5.4-STABLE #0: Wed Nov 23 15:16:09 EST 2005 ges@seibercom.net:/usr/obj/usr/src/sys/SEIBERCOM3 i386 I contacted the maintainer regarding this problem, and this was his response. ---------------------- Original Message Starts--------------------- From: Mikhail Teterin Congratulations! You have found a bug in ICU (or in one of its self-tests). From your log: [...] ---[OK] ---/custrtrn/Test_widestrs cintltst in free(): error: page is already free Abort trap (core dumped) *** Error code 134 You can avoid the crash by removing the 'a' from your MALLOC_FLAGS. To fix the underlying problem, please, consider filing a bug report with ICU. I'll try to dig it up, but I'm a little swapmed at the moment :-( Thanks for the report. Yours, -mi --------------------- Original Message Ends -------------------- Since I have no idea how to remove a flag, other than the one that flies on the pole in my front lawn, I contacted the 'icu' staff and submitted a bug report. The following is their response. ----------------------- Original Message Starts ------------------- Please build a debuggable version of ICU, and supply a stack trace of the failure in the bug report. We can't reproduce this bug on other platforms with heap debuggers, and the test suite doesn't fail on other versions of FreeBSD. ----------------------- Original Message Ends -------------------- The entire build and attempted install log is available at this URL: http://www2.seibercom.net:9545/log/icu3-4 I would really appreciate it if someone could assist me with this problem. I know for a fact that I am not the only individual that cannot get 'icu-3.4' installed. If someone could instruct me on how to make a debuggable version and supply a stack trace of the failure it would be very much appreciated. Any other suggestions, etc. would be very much appreciated. This problem, by the way, is causing 'python-boost' not to build which causes 'kdeede3' not to build either. Thanks in advance! -- Gerard Seibert gerard@seibercom.net