Date: Fri, 8 Sep 2000 08:04:03 -0500 (CDT) From: Mike Meyer <mwm@mired.org> To: Ilia Chipitsine <ilia@cgu.chel.su> Cc: questions@freebsd.org Subject: Re: profiled libs Message-ID: <14776.58307.156684.646704@guru.mired.org> In-Reply-To: <47960590@toto.iv>
next in thread | previous in thread | raw e-mail | index | archive | help
Ilia Chipitsine writes: > is it safe to remove profiled libraries (/usr/lib/*_p*) ? > how can I figure out that some library is required for particular > aplication ? Generally, yes, except the correct regexp is "/usr/lib/lib*_p.a". If you're tracking -current (and possibly -stable), you can disable building them by adding "NOPROFILE=true" to /etc/make.conf. The profiled libs are identical to the non-profiled libs, except that they have code added to generate profiling data. They get linked instead of the non-profiled ones when you compile a program with profiling. If you're doing software development and expect to improve performance, profiling is an important part of that, so you should keep them. Otherwise, you probably never need them. If it turns out you did need them later, you can always rebuild them from the same source you build the non-profiled libs from. <mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14776.58307.156684.646704>