From owner-freebsd-current Tue Jan 8 7:43:16 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 C288637B402 for ; Tue, 8 Jan 2002 07:43:09 -0800 (PST) Received: by router.hackerheaven.org (Postfix, from userid 1000) id 3EAB11C15; Tue, 8 Jan 2002 16:42:25 +0100 (CET) Date: Tue, 8 Jan 2002 16:42:24 +0100 From: Emiel Kollof To: Dan Nelson Cc: freebsd-current@FreeBSD.ORG Subject: Re: Mutt segfaulting on current revisited... Message-ID: <20020108154224.GB32215@laptop.hackerheaven.org> References: <20020108142732.GA29930@laptop.hackerheaven.org> <20020108153526.GA97613@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020108153526.GA97613@dan.emsphone.com> 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 * Dan Nelson (dnelson@allantgroup.com) wrote: > > 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? > > Actually, you should have gotten a linker warning about having > dependencies on multiple versions of a library. Usually it'll just > fail to link though. Well, it didn't fail, and I never saw that linker warning. I spend quite some time with a Mutt developer going back and forth, and trying out different stuff. I decided to build mutt and its dependancies again which solved the problem. Maybe the linker warning scolled by too fast. Well at least my trusty mutt works now :-) I do have COMPAT4X in my make.conf though... Maybe that had something to do with it? Cheers, Emiel -- "What is wanted is not the will to believe, but the will to find out, which is the exact opposite." -- Bertrand Russell, "Skeptical_Essays", 1928 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message