From owner-freebsd-current Tue Jan 8 7:35:35 2002 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id A1F5337B405 for ; Tue, 8 Jan 2002 07:35:30 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.11.6/8.11.6) id g08FZRT12631; Tue, 8 Jan 2002 09:35:27 -0600 (CST) (envelope-from dan) Date: Tue, 8 Jan 2002 09:35:26 -0600 From: Dan Nelson To: Emiel Kollof Cc: freebsd-current@FreeBSD.ORG Subject: Re: Mutt segfaulting on current revisited... Message-ID: <20020108153526.GA97613@dan.emsphone.com> References: <20020108142732.GA29930@laptop.hackerheaven.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020108142732.GA29930@laptop.hackerheaven.org> User-Agent: Mutt/1.3.25i X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error 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 In the last episode (Jan 08), Emiel Kollof said: > 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. -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message