public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Kaushik Phatak <Kaushik.Phatak@kpitcummins.com>
Cc: nick clifton <nickc@redhat.com>, Tom Tromey <tromey@redhat.com>,
	       "binutils@sourceware.org" <binutils@sourceware.org>,
	       "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	       Joel Brobecker <brobecker@adacore.com>
Subject: Re: [RFA] New port: CR16: BFD Changes required by the gdb port
Date: Tue, 08 Jan 2013 17:54:00 -0000	[thread overview]
Message-ID: <50EC5D58.3010503@redhat.com> (raw)
In-Reply-To: <C6CA53A2A46BA7469348BDBD663AB65848565B08@KCHJEXMB02.kpit.com>

On 01/08/2013 11:24 AM, Kaushik Phatak wrote:
> Hi Nick,
> Thanks for applying these changes with appropriate Changelogs.
> 
> I noticed that the entries for cr16 were missing in the latest gdb snapshot
> in configure.ac and configure.
> 
>   cr16-*-*)
>     noconfigdirs="$noconfigdirs gdb"
>     ;;
> This entry is present in the 7.5 release version of gdb but not
> in the latest snapshot, gdb-7.5.50.20130108
> 
> How is this controlled, in gcc or here? Could you please throw some light on this.

On gdb's git mirror, I see:

commit ce3c5eda0b8d664790bc633a1013193a3289dff0
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Sun Aug 26 14:34:38 2012 +0000

    Sync toplevel files with GCC tree

...
-  cr16-*-*)
-    noconfigdirs="$noconfigdirs gdb"
-    ;;
   d10v-*-*)
     noconfigdirs="$noconfigdirs target-libgloss"
     ;;
@@ -924,7 +939,8 @@ case "${target}" in
     noconfigdirs="$noconfigdirs libgui itcl ld"
     ;;
   ia64*-*-*vms*)
-    noconfigdirs="$noconfigdirs libgui itcl"
+    # No ld support yet.
+    noconfigdirs="$noconfigdirs libgui itcl ld"
     ;;
   i[[3456789]]86-w64-mingw*)
     ;;
@@ -1069,16 +1085,13 @@ case "${host}" in
   *-mingw*)
     host_makefile_frag="config/mh-mingw"
     ;;
-  *-interix*)
-    host_makefile_frag="config/mh-interix"
-    ;;
   hppa*-hp-hpux10*)
     host_makefile_frag="config/mh-pa-hpux10"
     ;;
   hppa*-hp-hpux*)
     host_makefile_frag="config/mh-pa"
     ;;
-  hppa*-*)
+  hppa*-*)
     host_makefile_frag="config/mh-pa"
     ;;

Dunno why these were removed with that merge.  The
ChangeLog entries brought in don't seen to
mention these changes.  Maybe it was a merge error
where local binutils changes were lost?

> Please let me know if I need to submit any patch for this as couple of hunks
> from my gdb patch are failing due to this.

Please always base the work you submit against the current
development mainline.  For GDB, that is:

 http://sourceware.org/gdb/current/

-- 
Pedro Alves

  reply	other threads:[~2013-01-08 17:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26  7:04 Kaushik Phatak
2012-12-14 18:52 ` Pedro Alves
2012-12-28 12:18   ` Kaushik Phatak
2013-01-02 13:14     ` nick clifton
2013-01-03 11:16       ` Kaushik Phatak
2013-01-07 15:11         ` nick clifton
2013-01-08 11:24           ` Kaushik Phatak
2013-01-08 17:54             ` Pedro Alves [this message]
2013-01-15  9:24               ` Kaushik Phatak
2013-01-02 14:19     ` Tom Tromey

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=50EC5D58.3010503@redhat.com \
    --to=palves@redhat.com \
    --cc=Kaushik.Phatak@kpitcummins.com \
    --cc=binutils@sourceware.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nickc@redhat.com \
    --cc=tromey@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).