X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Date: Mon, 03 Dec 2001 21:35:22 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Message-Id: <2110-Mon03Dec2001213522+0200-eliz@is.elta.co.il>
X-Mailer: emacs 21.1.50 (via feedmail 8 I) and Blat ver 1.8.9
CC: djgpp-workers AT delorie DOT com
In-reply-to: <Pine.LNX.4.10.10112031830250.8155-100000@acp3bf> (message from
	Hans-Bernhard Broeker on Mon, 3 Dec 2001 18:53:27 +0100 (MET))
Subject: Re: Building a profiled version of libc
References:  <Pine DOT LNX DOT 4 DOT 10 DOT 10112031830250 DOT 8155-100000 AT acp3bf>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> Date: Mon, 3 Dec 2001 18:53:27 +0100 (MET)
> From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
> 
> As I see it, the original question was how to make use of the profiling
> version of libc, once we're sure we know how to build one.  To use it
> seamlessly, we should edit the specs file to make GCC look for libc_p.a in
> -pg mode (or -profile, if we were to follow Linux here).

Yes.

And the problem is that specs is in the GCC distribution, while
libc_p.a, if we decide to distribute one, will be in djdev.

What I was saying was that these two changes must be in sync,
otherwise users will have broken installations.  At the very least,
we must release djdev with libc_p.a first, and modify specs some time
after that.

Until these two changes happen, users will have to make manual
changes in their configuration files, so this is not something we
could recommend to the general user.