X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Date: Tue, 4 Dec 2001 10:07:14 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
cc: djgpp-workers AT delorie DOT com,
   Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Subject: Re: Distribution issues (was: Re: Building a profiled version of libc)
In-Reply-To: <10112032126.AA14791@clio.rice.edu>
Message-ID: <Pine.SUN.3.91.1011204100656.25578G@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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


On Mon, 3 Dec 2001, Charles Sandmann wrote:

> When we refresh 2.03, should we put a stub libc_p.a in there?

I don't think so.  Not unless we want to make -pg related changes in
specs right away, in the next release of the ported GCC.

Also, a stub libc_p.a woul hardly help, since libc_p.a is supposed to
be linked _instead_ of libc.a, not _in_addition_ to it.

> By the way, should the .dsm be in the .mft?

If you mean that the contents of the .dsm file should be in the .mft
file, then I don't think so: *.mft are supposed to hold a list of
files only.

If you mean in what directory to put the .dsm, then it indeed should
be in manifest/.