From owner-freebsd-current Tue Jan 8 6:28: 4 2002 Delivered-To: freebsd-current@freebsd.org Received: from router.hackerheaven.org (qn-213-73-194-22.quicknet.nl [213.73.194.22]) by hub.freebsd.org (Postfix) with ESMTP id 025BD37B405 for ; Tue, 8 Jan 2002 06:28:01 -0800 (PST) Received: by router.hackerheaven.org (Postfix, from userid 1000) id 85C351C15; Tue, 8 Jan 2002 15:27:33 +0100 (CET) Date: Tue, 8 Jan 2002 15:27:32 +0100 From: Emiel Kollof To: freebsd-current@freebsd.org Subject: Mutt segfaulting on current revisited... Message-ID: <20020108142732.GA29930@laptop.hackerheaven.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.25i X-Mailer: Mutt 1.3.23i (2001-10-09) X-Editor: Vim http://www.vim.org/ X-Info: http://www.hackerheaven.org/ X-Info2: http://www.cmdline.org/ X-Info3: http://www.coolvibe.org/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hey folks... I just found out why my mutt MUA segfaulted. It came down to old libs lying around that were still linked with libc4 instead of libc5. Mutt (from mutt-devel port) compiled beautifully, but it segfaulted on startup. Could this be one for the FAQ or something? Maybe explaining library differences between STABLE and CURRENT and you should be extra careful when an app mixes libc4 and libc5? I solved my problem by recompiling the dependancy libraries (in my case libiconv and libslang) so they use libc5 as well. As you can see from my X-Mailer header, mutt works again :-) Cheers, Emiel -- When the Universe was not so out of whack as it is today, and all the stars were lined up in their proper places, you could easily count them from left to right, or top to bottom, and the larger and bluer ones were set apart, and the smaller yellowing types pushed off to the corners as bodies of a lower grade ... -- Stanislaw Lem, "Cyberiad" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message