All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geoffrey Wossum <geoffrey@pager.net>
To: openembedded-devel@lists.openembedded.org
Subject: avr32-*-gdb requires modifying gdb.inc / gdb-cross.inc
Date: Wed, 9 Apr 2008 09:20:02 -0500	[thread overview]
Message-ID: <200804090920.02871.geoffrey@pager.net> (raw)

Hi all,

I currently have a BitBake recipe that can build gdb 6.4 for the AVR32, and 
I'm about to make one that can build the gdb 6.7 using Atmel's newly released 
patches for the AVR32.

According to this page, http://avr32linux.org/twiki/bin/view/Main/GDBPatches, 
you must do some extra steps to build gdb if you patch it.  My experience 
with Atmel's gdb 6.4 release was that even though they claim you don't have 
to do these steps if you use the full source tarball, you have to anyway.

This requires modifying gdb.inc / gdb-cross.inc.  I think the modifications 
are safe for all platforms, but I was hoping someone could comment before I 
roll a patchset to submit.  

TIA,
---
Geoffrey


--- packages/gdb/gdb-cross.inc  2008-03-04 14:30:27.000000000 -0600
+++ /home/geoff/lrs/playpaq/org.openembedded.dev/packages/gdb/gdb-cross.inc    
2008-04-09 09:09:50.000000000 -0500
@@ -10,9 +10,38 @@ do_configure () {
 # override this function to avoid the autoconf/automake/aclocal/autoheader
 # calls for now
        (cd ${S} && gnu-configize) || die "failure in running gnu-configize"
+
+
+        # This stuff is required to build Atmel's patched gdb for the AVR32.
+        # See http://avr32linux.org/twiki/bin/view/Main/GDBPatches
+        (cd ${S}/bfd && autoreconf) || die "failure running autoreconf in bfd/"
+        (cd ${S}/opcodes && autoreconf) || die "failure running autoreconf in opcodes/"
+
        oe_runconf
+
+
+        # Also required according to the avr32linux GDBPatches page
+        make configure-bfd || die "Error running configure-bfd"
+        (cd bfd && make headers && cd "$OLDPWD") || \
+                die "error running 'make headers' in bfd"
 }

 do_stage () {
+        # Left to fend for itself, "make install" will fail, saying that
+        # makeinfo is missing.  I don't know if this is because my system
+        # makeinfo isn't available inside the bitbake build, or if this is
+        # due to the texinfo version detection bug that has plagued some
+        # packages (see https://bugzilla.redhat.com/show_bug.cgi?id=345621).
+        # Either way, we want to keep "make install"from wanting to run
+        # makeinfo.  By copying over all the .info files before hand,
+        # the files will exist in the build tree and have shiny new
+        # timestamps, thus preventing "make install" from using makeinfo.
+        cd ${S}
+        for infofile in `find . -name "*.info"`; do
+            cp "$infofile" ${B}/"$infofile"
+        done
+        cd "$OLDPWD"
+
+
        oe_runmake install
 }







             reply	other threads:[~2008-04-09 14:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09 14:20 Geoffrey Wossum [this message]
2008-04-09 15:07 ` avr32-*-gdb requires modifying gdb.inc / gdb-cross.inc Khem Raj
2008-04-09 15:49   ` Geoffrey Wossum

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=200804090920.02871.geoffrey@pager.net \
    --to=geoffrey@pager.net \
    --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.