From owner-freebsd-questions@FreeBSD.ORG Sun Sep 2 14:36:57 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 71A6A16A41B; Sun, 2 Sep 2007 14:36:57 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id 8C3A713C46A; Sun, 2 Sep 2007 14:36:56 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46DACA87.8080709@FreeBSD.org> Date: Sun, 02 Sep 2007 16:36:55 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Kris Kennaway , Kris Kennaway , freebsd-questions@freebsd.org References: <20070822042246.GA3497@saturn.pcs.ms> <20070822043725.GA2869@rot26.obsecurity.org> <20070822045118.GB3497@saturn.pcs.ms> <20070822063102.GA4141@rot26.obsecurity.org> <20070822064430.GB3852@saturn.pcs.ms> <20070822132050.GA9055@rot26.obsecurity.org> <20070826153546.GA637@saturn.pcs.ms> <20070827153454.GB70070@hub.freebsd.org> <20070902115924.GA38350@saturn.pcs.ms> In-Reply-To: <20070902115924.GA38350@saturn.pcs.ms> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: ldconfig problem after upgrade 4.11 to 5.5 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Sep 2007 14:36:57 -0000 Martin Schweizer wrote: > Hello Kris > > Am Mon, Aug 27, 2007 at 03:34:54PM +0000 Kris Kennaway schrieb: >>>>>>>>> After I updated my 4.11 to an 5.5 system (following /usr/src/UPDATING), I get >>>>>>>>> around 63 error messages while the system boot up: >>>>>>>>> >>>>>>>>> ldconfig: /var/run/ld.so.hints: No such file or directory >>>>>>>>> search: trailing characters ignored >>>>>>>>> No such file or directory >>>>>>>>> 0: - lmalloc.1.1: trailing characters ignored. No such file or >>>>>>>>> directory >>>>>>>>> ... >>>>>>>>> ... >>>>>>>>> >>>>>>>> Looks like it might be a broken symlink. >>>>>>>> >>>>>>>> Why are you updating to 5.5 though? You should be using 6.2. >>>>>>> If I'm understanding /usr/src/UPDATING correct I should first update to 5.5 >>>>>>> and then to 6.2? >>>>>> OK. It may have been easier (and still could be) to just do a binary >>>>>> upgrade instead. >>>>>> >>>>>>> Any ideas where I can check this symlink? >>>>>> Use find(1) to look for libmalloc.so.1.1 >>>>> The files are all located in /usr/lib/compat/aout. The path is defined in >>>>> /etc/defaults/rc.conf >>>>> [snip] >>>>> ldconfig_paths_aout="/usr/lib/compat/aout /usr/X11R6/lib/aout /usr/local/lib/aout" >>>>> [snip] >>>>> >>>>> Any ideas? >>>> Are you missing aout support from your kernel? I think it's COMPAT_AOUT. >>> After reading about ldconfig and playing with the parameters (see man page) I >>> find out that the processing of the pathes in /etc/defaults/rc.conf isn't >>> correct. >>> /etc/defaults/rc.conf: >>> [snip] >>> ldconfig_insecure="NO" # Set to YES to disable ldconfig security checks >>> ldconfig_paths="/usr/lib/compat /usr/X11R6/lib /usr/local/lib" >>> ldconfig_paths_aout="/usr/lib/compat/aout /usr/X11R6/lib/aout /usr/local/lib/aout" >>> ldconfig_local_dirs="/usr/local/libdata/ldconfig /usr/X11R6/libdata/ldconfig" >>> # Local directories with ldconfig configuration files. >>> ldconfig_local32_dirs="/usr/local/libdata/ldconfig32 /usr/X11R6/libdata/ldconfig32" >>> # Local directories with 32-bit compatibility ldconfig >>> [snip] >>> >>> Following this I set in /etc/rc.conf >>> >>> [snip] >>> ldconfig_paths_aout="/usr/lib/compat/aout" >>> [snip] >>> >>> Any ideas why the kernel do not process the pathes correct? >>> >>> Now it works. Thank you for your help. >>> >> You need a.out support *IN YOUR KERNEL*. i.e. you need to enable it >> in your kernel configuration and recompile your kernel. > > Only for clarification. This option I've in my kernel: > [snip] > options COMPAT_AOUT > [snip] > > After the above change in /etc/rc.conf no messages occurs while FreeBSD is > starting. OK great, thanks for confirming. Kris