From owner-freebsd-current Sun Jan 28 11:28:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from gypsy.vrac.iastate.edu (gypsy.vrac.iastate.edu [129.186.232.122]) by hub.freebsd.org (Postfix) with ESMTP id 5728C37B69B for ; Sun, 28 Jan 2001 11:28:04 -0800 (PST) Received: from tomservo.vrac.iastate.edu (tomservo.vrac.iastate.edu [129.186.232.121]) by gypsy.vrac.iastate.edu (Postfix) with ESMTP id 96ABA1A; Sun, 28 Jan 2001 13:28:04 -0600 (CST) Received: from tomservo.vrac.iastate.edu (localhost [127.0.0.1]) by tomservo.vrac.iastate.edu (Postfix) with ESMTP id 297935E30; Sun, 28 Jan 2001 13:28:03 -0600 (CST) To: Jeroen Ruigrok van der Werven Cc: freebsd-current@FreeBSD.ORG Subject: Re: Fixed: LyX 1.1.5.2 dumping core In-reply-to: "Sun, 28 Jan 2001 12:52:34 +0100." <20010128125234.A68355@lucifer.bart.nl> Date: Sun, 28 Jan 2001 13:28:03 -0600 From: Patrick Hartling Message-Id: <20010128192803.297935E30@tomservo.vrac.iastate.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok van der Werven wrote: } -On [20010127 22:30], Patrick Hartling (patrick@137.org) wrote: } >Making a symlink from /usr/lib/libc.so.5 to /usr/lib/libc.so.3 seems to } >have fixed my LyX problems. I'm guessing libc.so.5 and libc.so.3 were } >causing conflicts, especially with the recent changes to libc, but I'm no } >expert. Whatever the case, I can get back to work on my thesis now. :) } } Have you tried recompiling LyX with the new libc? I did try that initially, but the problems persisted until I made the symlink and relinked the executable. } That should normally clear any problems. } } I suspect from what you said above, that when you do ldd `which lyx` it } will report lyx being linked against libc.so.3, but for some reason is } trying to use the higher version libc. ldd was telling me that it had both libc.so.3 and libc.so.5 which seemed very bad to me. When I recomipled LyX to see if that would fix things, I noticed that ld was giving a warning about libc.so.3 and libc.so.5 potentially conflicting. It hadn't ever been a problem before, but it doesn't seem like the safest arrangment. With the symlink in place, ldd reports that only libc.so.5 is being used, and everything seems to be okay. -Patrick Patrick L. Hartling | Research Assistant, VRAC patrick@137.org | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message