Date: Sat, 31 Jan 2015 03:50:39 +1030 From: Shane Ambler <FreeBSD@ShaneWare.Biz> To: =?UTF-8?B?TWFya28gQ3VwYcSH?= <marko.cupac@mimar.rs>, freebsd-stable@freebsd.org Subject: Re: freebsd-update and lib32 Message-ID: <54CBBD67.5060404@ShaneWare.Biz> In-Reply-To: <20150130145033.9c6459154a028e17b2f03f7f@mimar.rs> References: <20150130145033.9c6459154a028e17b2f03f7f@mimar.rs>
next in thread | previous in thread | raw e-mail | index | archive | help
On 31/01/2015 00:20, Marko Cupać wrote: > Hi, > > for years I've been leaving default 'lib32' option during initial > install of FreeBSD selected, but now I am experimenting with a server > which will be 64-bit only. > > I have noticed that, after initial install of FreeBSD 10.1-RELEASE > without lib32 selected, /usr/lib32 folder is created nevertheless, > containing 3 empty dirs: dtrace, i18n and private. However, running > freebsd-update on such system pulls a bunch of files into /usr/lib32 > and its subdirs while updating to FreeBSD 10.1-RELEASE-p5. Doing a buildworld WITHOUT_LIB32 still creates these dirs. I reported it a while back but it is still on someones todo list. Not sure if that is also related to freebsd-update or is the cause of it triggering the lib32 install. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165175 > Are those files really necessary on 64-bit only system? No they aren't needed, you can delete /usr/lib32 without any problems. I have been deleting it for a few years now without issue. In fact deleting it may fix some port builds, such as older versions of valgrind tested for lib32 to determine if it builds 32bit libs and failed if lib32 was empty, the new version now has an option for 32bit. I just keep `rm -R /usr/lib32` as a step in my notes on updating. -- FreeBSD - the place to B...Software Developing Shane Ambler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54CBBD67.5060404>