All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Building multiple gdb-cross targets
Date: Fri, 04 Apr 2008 10:48:59 -0700	[thread overview]
Message-ID: <47F66A0B.1000904@gmail.com> (raw)
In-Reply-To: <200804041057.55738.geoffrey@pager.net>

[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]

Geoffrey Wossum wrote:
> Hi all,
> 
> Another question about build gdb-cross for the AVR32.  Building gdb-cross gets 
> me avr32-angstrom-linux-uclibc-gdb.  But over at this page, 
> http://avr32linux.org/twiki/bin/view/Main/KernelDebugging, it says you really 
> want an standalone gdb for kernel debugging.
> 
> How can I get OE to build just an avr32-gdb?  How can I get OE to build both 
> avr32-gdb and avr32-linux-gdb (aka avr32-angstrom-linux-uclibc-gdb)?  

They are two different configurations of gdb the one OE will build for 
you is the cross gdb which is supposed to cross debug linux applications 
(e.g. arm-*-linux-gnueabi). The one you are intending to have is what I 
call baremetal (e.g. arm-eabi)  debugger. I dont think you will be able 
to build this with ease using OE as they are really two different 
targets for OE to build.

Why would avr-linux gdb not work ?

HTH

-Khem


> 
> TIA,
> ---
> Geoffrey
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 258 bytes --]

  reply	other threads:[~2008-04-04 17:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04 15:57 Building multiple gdb-cross targets Geoffrey Wossum
2008-04-04 17:48 ` Khem Raj [this message]
2008-04-04 18:46   ` Geoffrey Wossum
2008-04-04 20:54     ` Leon Woestenberg
2008-04-07 14:53       ` Geoffrey Wossum
2008-04-07 14:54     ` Geoffrey Wossum
2008-04-07 17:58       ` Stelios Koroneos
2008-04-07 18:54         ` Geoffrey Wossum
2008-04-07 20:23           ` Leon Woestenberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47F66A0B.1000904@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.