Mirror of the gdb mailing list
 help / color / mirror / Atom feed
* Need advice on building GDB for a large number of PowerPC variants.
@ 2007-05-17 21:43 Anmol P. Paralkar
       [not found] ` <655C3D4066B7954481633935A40BB36F041300@ussunex02.svl.access-company.com>
  0 siblings, 1 reply; 2+ messages in thread
From: Anmol P. Paralkar @ 2007-05-17 21:43 UTC (permalink / raw)
  To: gdb

Hello,

  I need to build GDB for a debugging a variety of PowerPC families.
  The host environment is x86 plus a small subset of the PowerPC
  variants. GDB will be used native as well as cross (remote) from
  each host (x86 (cross-only) as well as PowerPC). A substantial
  number of PowerPC flavours is desired to be targetted - the number
  of families and the instances within each family all result in a
  fairly large number of individual targets. Both the variations in
  configurations: powerpc-linux-gnu as well as powerpc-eabi are needed
  for almost each individual target.

  I reckon that I only need build:

  * GDB in both eabi and linux configurations per host; any desired
    target can be debugged by doing a 'set architecture' for it.

    That way the number of GDB's built is two per host.

  as against:

  * A GDB per (host, target) combination of interest.

    Which will needless to say, will result in a large number of
    GDB executables needed to be built.

  Please could you tell me if my reasoning is correct or am I missing
  something essential?

  Thank you very much for your help.

Best Regards,
Anmol P. Paralkar


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-05-18 13:51 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-05-17 21:43 Need advice on building GDB for a large number of PowerPC variants Anmol P. Paralkar
     [not found] ` <655C3D4066B7954481633935A40BB36F041300@ussunex02.svl.access-company.com>
2007-05-18 13:51   ` Anmol P. Paralkar

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox