Date: Wed, 16 Oct 2002 13:23:21 -0400
Message-Id: <200210161723.g9GHNLS04335@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp AT delorie DOT com
In-reply-to: <3DAD9A14.70C1CD1E@cyberoptics.com> (message from Eric Rudd on
	Wed, 16 Oct 2002 11:55:48 -0500)
Subject: Re: symify problem
References: <3DAD80B7 DOT 98C390C1 AT cyberoptics DOT com> <200210161537 DOT g9GFbs302995 AT envy DOT delorie DOT com> <3DAD9A14 DOT 70C1CD1E AT cyberoptics DOT com>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> Would it make sense to include bfdsymify in DJDEV203.ZIP,

No, because bfdsymify requires bfd, and djdev should not depend on bfd.

> and get rid of the old symify?

Maybe, maybe not.  It's handy to have a smaller version that at least
handles functions, and perhaps someone will add support for the newer
debug formats some day.

Alternately, symify could look to see if bfdsymify is in your path,
and exec it if found.