X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Date: Sun, 2 Dec 2001 14:50:31 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
cc: djgpp-workers AT delorie DOT com
Subject: Re: Building a profiled version of libc
In-Reply-To: <3C0A0D35.B45C0E74@phekda.freeserve.co.uk>
Message-ID: <Pine.SUN.3.91.1011202144745.9372A-100000@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 Sun, 2 Dec 2001, Richard Dawe wrote:

> Error: object contains unresolved external symbols (start)
> Error: object contains unresolved external symbols (__stubinfo)
> Error: object contains unresolved external symbols (_main)
> make.exe: *** [../../bin/emu387.dxe] Error 17
> 
> Clearly using a profiling libc pulls in symbols that require a program's
> link environment. I don't think there is going to be a good way of fixing
> without building both normal and profile versions of the library and then
> linking against the normal library.

Building a library twice is a pain.  If emu387 cannot be profiled, simply 
don't rebuild it when -pg is in the switches.

> Has there been much demand for a profiling version of 2.03? (I'm guessing
> that there hasn't.)

People were asking about this from time to time.