This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Best way to add DBX_USE_BINCL to a.out toolchains?
- To: Geoff Keating <geoffk at geoffk dot org>
- Subject: Re: Best way to add DBX_USE_BINCL to a.out toolchains?
- From: jtc at redback dot com (J.T. Conklin)
- Date: 07 Jun 2001 10:46:40 -0700
- Cc: gcc at gcc dot gnu dot org
- References: <5mhextb56m.fsf@jtc.redback.com> <jm1yowlu2z.fsf@geoffk.org>
- Reply-To: jtc at redback dot com
>>>>> "Geoff" == Geoff Keating <geoffk@geoffk.org> writes:
>> My question is what is the best way to do this. I don't know if it's
>> safe to just define DBX_USE_BINCL (will the extra stabs be ignored on
>> old (or non-gnu) linkers that don't understand BINCL/EINCL?), or if
>> separate configs are necessary. If separate configs are necessary,
>> should I trigger off --with-gnu-ld?
Geoff> The real question is "will the extra stabs be ignored by non-gdb
Geoff> debuggers, like dbx?"
Exactly.
I suspect adding DBX_USE_BINCL to the i386-aout and m68k-aout targets
is probably safe. Considering the absense of any E/ABIs, I would not
expect objects from different vendors tools to be compatible. I seem
to recall that it took a few iterations for vendors to get everything
in sync when there are E/ABIs.
--jtc
--
J.T. Conklin
RedBack Networks