Date: Sun, 28 Jan 2001 12:52:34 +0100 From: Jeroen Ruigrok van der Werven <jruigrok@via-net-works.nl> To: Patrick Hartling <patrick@137.org> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Fixed: LyX 1.1.5.2 dumping core Message-ID: <20010128125234.A68355@lucifer.bart.nl> In-Reply-To: <20010127212514.AF1425E2C@tomservo.vrac.iastate.edu>; from patrick@137.org on Sat, Jan 27, 2001 at 03:25:14PM -0600 References: <20010127184654.C42CD5E32@tomservo.vrac.iastate.edu> <20010127212514.AF1425E2C@tomservo.vrac.iastate.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
-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? 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. -- Jeroen Ruigrok van der Werven VIA Net.Works The Netherlands BSD: Technical excellence at its best Network- and systemadministrator D78D D0AD 244D 1D12 C9CA 7152 035C 1138 546A B867 Misery loves company... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010128125234.A68355>