From owner-freebsd-questions Fri Sep 8 6: 4:43 2000 Delivered-To: freebsd-questions@freebsd.org Received: from guru.mired.org (zoom1-170.telepath.com [216.14.1.170]) by hub.freebsd.org (Postfix) with SMTP id DC47937B422 for ; Fri, 8 Sep 2000 06:04:40 -0700 (PDT) Received: (qmail 71443 invoked by uid 100); 8 Sep 2000 13:04:03 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14776.58307.156684.646704@guru.mired.org> Date: Fri, 8 Sep 2000 08:04:03 -0500 (CDT) To: Ilia Chipitsine Cc: questions@freebsd.org Subject: Re: profiled libs In-Reply-To: <47960590@toto.iv> X-Mailer: VM 6.72 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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.