Date: Thu, 14 Aug 2008 10:34:26 +0200 From: =?ISO-8859-1?Q?Morgan_Wesstr=F6m?= <freebsd-stable@pp.dyndns.biz> To: freebsd-stable@freebsd.org Subject: Re: Removing /usr/lib32 on AMD64 Message-ID: <48A3EE12.7060302@pp.dyndns.biz> In-Reply-To: <20080814081309.GA8249@eos.sc1.parodius.com> References: <48A3E29D.3090504@pp.dyndns.biz> <20080814081309.GA8249@eos.sc1.parodius.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for your answer Jeremy :-) > What you've documented above is the Correct Way(tm) to remove lib32 > support. Though I advocate people not install it in the first place, > unless they absolutely need it. I'm not sure I was ever given the option to deselect it during sysinstall. I don't rememeber any obvious question at least and /etc/src.conf did not exist efter install. > The message from /etc/rc.d/ldconfig you see there about 32-bit > compatibility ldconfig path is fine -- it shows an empty path, which is > correct. Nothing to worry about there. There are references in ldconfig to a couple of options I find in /etc/defaults/rc.conf ldconfig32_paths="/usr/lib32" # 32-bit compatibility shared library ldconfig_local32_dirs="/usr/local/libdata/ldconfig32" Should I blank those? /usr/local/libdata/ldconfig32 is an empty folder here. There's also a /libexec/ld-elf32.so.1 left, with the same old date as the libs, and a symlink from /usr/libexec/ld-elf32.so.1 pointing to it. Should I leave them or remove them? They were not mentioned in the diff in the bugreport. /Morgan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48A3EE12.7060302>