Date: Fri, 20 Sep 2002 16:10:11 +1000 From: "Michael Wardle" <michael.wardle@adacel.com> To: "Kosta K" <kosta_k@phreaker.net> Cc: <freebsd-stable@freebsd.org> Subject: Re: /usr/X11R6/lib/libGLU.so.1 is not a symbolic link Message-ID: <001701c2606c$61173300$354ba8c0@wodonga.adacel.com.au> References: <002301c26062$35e77d20$2900a8c0@kostawkst>
next in thread | previous in thread | raw e-mail | index | archive | help
> Sep 10 12:57:09 browser /kernel: Additional ABI support: > Sep 10 12:57:09 browser /kernel: linux As you would have guessed, naturally this suggests the problem is related to the FreeBSD Linux compatibility service. > Sep 10 12:57:11 browser /kernel: /compat/linux/sbin/ldconfig: > Sep 10 12:57:11 browser /kernel: /usr/X11R6/lib/libGLU.so.1 is not a > symbolic link > Sep 10 12:57:11 browser /kernel: > Sep 10 12:57:11 browser /kernel: /compat/linux/sbin/ldconfig: > Sep 10 12:57:11 browser /kernel: /usr/X11R6/lib/libGL.so.1 is not a symbolic > link On Linux, shared objects (libraries) are expected to be of the form lib<name>.so.<major>.<minor>.<point>, whereas on FreeBSD the file has no minor or point release number in the file name as far as I know. From the little I understand of ldconfig, my guess is that /etc/ld.so.conf (or wherever the Linux version of that file is, perhaps somewhere under /compat) has /usr/X11R6/lib listed as a shared library path, and that when the Linux compatibility service is started, ldconfig is run to update the shared library cache. The easy way of stopping this error message from appearing is to remove /usr/X11R6/lib from the Linux ld.so.conf, but this will probably mean you can't run any X-related Linux applications. Another workaround could be to move libGLU.so.1 to a file reflecting its full version number (such as libGLU.so.1.2.2), and then creating the appropriate symbolic link, however: a) this could cause problems with native FreeBSD apps b) it's possible that the error occurs with libGLU simply because it appears first in a directory listing of /usr/X11R6/lib, and you might then need to rename/move all shared libraries in that directory Another obvious suggestion is if you don't want Linux compatibility it can be turned off by changing its entry in /etc/rc.conf. I would wonder whether the FreeBSD version of Linux's ldconfig should support both FreeBSD-style and Linux-style library names. Did you previously have FreeBSD and Linux compatibility working? Was something changed recently? Perhaps you added/made/ downloaded a port/package that needed Linux compatibility. In the case that this could be a bug in FreeBSD or in FreeBSD Linux compatibility, perhaps it would be useful if you provided information regarding which FreeBSD release you are running and which version of the Linux compatibility package you are using. Sorry I can't be of more help, but maybe I've provided a little more information so that someone else can. -- MICHAEL WARDLE SGI Desktop and Sysadmin Software Adacel Technologies Limited To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001701c2606c$61173300$354ba8c0>