-Original Message-
From: Roland Smith [mailto:[EMAIL PROTECTED]
Sent: 21 June 2005 19:07
To: Harrison Peter CSA BIRKENHEAD
Cc: freebsd-questions@freebsd.org
Subject: Re: -DNOPROFILE with make buildworld...
On Tue, Jun 21, 2005 at 01:49:06PM +0100, Harrison Peter CSA
BIRKENHEAD
-Original Message-
From: Chuck Swiger [mailto:[EMAIL PROTECTED]
Sent: 21 June 2005 19:25
To: Roland Smith
Cc: Harrison Peter CSA BIRKENHEAD; freebsd-questions@freebsd.org
Subject: Re: -DNOPROFILE with make buildworld...
[snip]
Normally, you don't use the profiled versions
On Wed, Jun 22, 2005 at 09:46:11AM +0100, Harrison Peter CSA BIRKENHEAD wrote:
-Original Message-
From: Chuck Swiger [mailto:[EMAIL PROTECTED]
Sent: 21 June 2005 19:25
To: Roland Smith
Cc: Harrison Peter CSA BIRKENHEAD; freebsd-questions@freebsd.org
Subject: Re: -DNOPROFILE
-Original Message-
From: Erik Trulsson [mailto:[EMAIL PROTECTED]
Sent: 22 June 2005 10:11
To: Harrison Peter CSA BIRKENHEAD
Cc: Chuck Swiger; freebsd-questions@freebsd.org
Subject: Re: -DNOPROFILE with make buildworld...
[snip]
Most of the apps I'm running have been compiled from
with -DNOPROFILE (or
specifying it in make.conf). I'm not clear what the impact of running profiled
libraries is against non-profiled libraries. I've done a quick search via
google and through the list archives without success.
Could anyone explain the difference for me briefly so that I can make
On Tue, Jun 21, 2005 at 01:49:06PM +0100, Harrison Peter CSA BIRKENHEAD wrote:
I've cvsup'ed my source tree, and stepping through the instructions in
the handbook I note that it recommends running make buildworld with
-DNOPROFILE (or specifying it in make.conf). I'm not clear what the
impact
Roland Smith wrote:
On Tue, Jun 21, 2005 at 01:49:06PM +0100, Harrison Peter CSA BIRKENHEAD wrote:
I've cvsup'ed my source tree, and stepping through the instructions in
the handbook I note that it recommends running make buildworld with
-DNOPROFILE (or specifying it in make.conf). I'm
Geert Hendrickx wrote:
What exactly does this make.conf-flag do:
NOPROFILE= true# Avoid compiling profiled libraries
What are profiled libraries?
GH
___
[EMAIL PROTECTED] mailing list
Hi,
I was wondering what this make.conf-flag is for:
NOPROFILE= true# Avoid compiling profiled libraries
What are profiled libraries?
GH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To
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)
GH
--
Cordula's Web.
?
/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
or benchmarker), I don't need this and can
use -DNOPROFILE for not building profiled libraries?
Yes, that's the whole point of NOPROFILE. Unless you are a developer
yourself and want to optimize some code, there's little reason to keep
those profiling libs around (or spend time building them).
I also
Ok, thank you very much for enlightening me! :-)
GH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
What exactly does this make.conf-flag do:
NOPROFILE= true# Avoid compiling profiled libraries
What are profiled libraries?
GH
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe,
14 matches
Mail list logo
