Date: Thu, 9 Sep 2004 13:51:22 +0200 From: Geert Hendrickx <geert.hendrickx@ua.ac.be> To: cpghost@cordula.ws Cc: freebsd-questions@freebsd.org Subject: Re: what is -DNOPROFILE ? Message-ID: <20040909115122.GA52787@lori.mine.nu> In-Reply-To: <20040909114033.GA2039@bsdevil.farid-hajji.net> References: <20040909105232.GA51740@lori.mine.nu> <20040909114033.GA2039@bsdevil.farid-hajji.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Sep 09, 2004 at 01:40:33PM +0200, cpghost@cordula.ws wrote:
> On Thu, Sep 09, 2004 at 12:52:32PM +0200, Geert Hendrickx wrote:
> > Hi,
> >
> > I was wondering what this make.conf-flag is for:
> >
> > NOPROFILE= true # Avoid compiling profiled libraries
> >
> > What are "profiled" libraries?
>
> /usr/lib/lib*_p.{a,so}
>
> See gprof(1)
So, if I understand it correctly from gprof(1), profiled libraries are
for measuring how much CPU time is spent in each suboutine? And, as a
regular user (not a developer or benchmarker), I don't need this and can
use -DNOPROFILE for not building profiled libraries?
I also understand these libraries are seperate from my "regular"
libraries? So, is there a drawback (other than increased compile time
for a make world) in building them? Or does it not matter?
GH
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040909115122.GA52787>