Date: Sat, 1 Mar 2003 12:22:54 +0000 (UTC) From: naddy@mips.inka.de (Christian Weisgerber) To: freebsd-ports@freebsd.org Subject: Re: WARNING: portupgrade considered harmful Message-ID: <b3q8mu$gbs$1@kemoauc.mips.inka.de> References: <3E5FB1F8.4050405@mail.flyingcroc.net> <b3p0u6$kt$1@kemoauc.mips.inka.de> <200303010416.50699.michaelnottebrock@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Michael Nottebrock <michaelnottebrock@gmx.net> wrote: > > I don't understand this. /usr/local/lib/compat/pkg is not in ld's > > search path, why should it pick up libraries from there? > > Because portupgrade/portsclean runs ldconfig accordingly after > moving/deleting libraries. ldconfig sets ld-elf.so's search path. When you build a program, ld(1) picks the available libraries from its search path, which includes /usr/lib and everything you happen to specify with -L. When you run a program, ld-elf.so(1) will pick up the libraries from the search path set with ldconfig(8). Unless you foolishly build a program with -L/usr/local/lib/compat/pkg, the old libraries there will never be used when producing new executables. However, the dynamic linker will search the compat directory at execution time, so the old libraries are still available to old executables. I don't see how the problem under discussion can arise. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b3q8mu$gbs$1>