Date: Sat, 18 Nov 2000 09:20:52 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: djgpp-workers AT delorie DOT com
Message-Id: <7263-Sat18Nov2000092052+0200-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.6
CC: richdawe AT bigfoot DOT com
In-reply-to: <5.0.1.4.0.20001117161925.0256a340@pop5.banet.net>
	(pjfarley AT banet DOT net)
Subject: Re: Help: Isn't libdbg the debugging version of libc?
References: <5 DOT 0 DOT 1 DOT 4 DOT 0 DOT 20001116230739 DOT 00a55af0 AT pop5 DOT banet DOT net>
 <5 DOT 0 DOT 1 DOT 4 DOT 0 DOT 20001116230739 DOT 00a55af0 AT pop5 DOT banet DOT net>
 <5 DOT 0 DOT 1 DOT 4 DOT 0 DOT 20001117121959 DOT 03459ad0 AT pop5 DOT banet DOT net> <5 DOT 0 DOT 1 DOT 4 DOT 0 DOT 20001117161925 DOT 0256a340 AT pop5 DOT banet DOT net>
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: Fri, 17 Nov 2000 16:42:22 -0500
> From: "Peter J. Farley III" <pjfarley AT banet DOT net>
>  >
>  >I'm not suggesting this be incorporated into the DJGPP build, since
>  >it would add a dependency on sed, but it's a solution nonetheless.
> 
> But couldn't we depend on the existence of the bnu*.mft or bnu*.ver 
> file(s)?

That won't work on a Unix box, when the package is built/tested in a
cross-compiled environment.

I think it might be possible to replace Sed commands with a suitable
GNU Make magic, using the built-in string-manipulation functions.
Failing that, we could add some simple string-replace code to
misc.exe, and use that as a portable alternative to Sed.

> I'm no "as" expert at all, but is there not an assembly-time macro that 
> identifies the version?

We couldn't find one, I think.  Mark?

> Separately, do I need to make the "*" changes to the "exceptn.S" and 
> "dbgcom.c" files manually to be sure I'm building a correct libc?

Yes, that's what I would do.

Alternatively, you could compare the machine instructions generated by
your assembler with the machine instructions in the stock v2.03
library version of exceptn.S (you could use objdump for that).