On Thu, Aug 14, 2008 at 09:45:33AM +0200, Morgan Wesstr?m
wrote:> Hi.
>
> Looking through man src.conf I found the knob WITHOUT_LIB32 and
> recompiled my world with it since I have no use for 32-bit compatibility
> on my AMD64. After installworld I realized that /usr/lib32 was still
> there and still populated. Searching for information I found this
> bugreport:
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=117191&cat>
> Judging from that report and the fact that the dates on the files in
> /usr/lib32 wasn't updated I figured it was ok to simply remove them. I
> just want to make sure there's nothing else I have to do to cleanly
> remove 32-bit compatibility? I can see during boot that there is still
> some reference to 32-bit compatibility. The following message flashes by
> on the screen:
>
> ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib
> /usr/local/lib/mysql
> 32-bit compatibility ldconfig path:
>
> I can track the last row to /etc/rc.d/ldconfig but can't figure out if
> that script can take any options in /etc/rc.conf to stop looking for
> 32-bit libraries. There are no error messages what I can see so
> everything is probably ok, just want to make absolutely sure. Anyone who
> can share some insight on this?
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.
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.
My systems, which have never had lib32 ever, show the same:
ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib
/usr/local/lib/mysql
32-bit compatibility ldconfig path:
--
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |