Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mario Emmenlauer <mario@emmenlauer.de>
To: gdb@sourceware.org
Subject: Re: gdb supported on powerpc-apple-darwin ?
Date: Sat, 16 Aug 2008 22:07:00 -0000	[thread overview]
Message-ID: <48A6F7D2.1080601@emmenlauer.de> (raw)
In-Reply-To: <20080816150045.GA25832@caradoc.them.org>

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


Hi,

Daniel Jacobowitz wrote:
> On Sat, Aug 16, 2008 at 04:44:57PM +0200, Mario Emmenlauer wrote:
>> it seems a rather trivial question, however I could not easily find
>> the answer: is 'plain' FSF gdb supported on Mac OS X (ppc darwin)?
> 
> No.  That's what this means:
> 
>> *** This configuration is not supported in the following subdirectories:
>>      bfd opcodes gdb sim

Fair enough :-)

BTW: the error message appears just after invoking configure, and is
not re-displayed later. This is why I missed it the first time. When
the 'gdb' directory is not supported, it might be sensible to show a
big warning at the configure results?

A start might be something like the below patch to configure.ac.


Cheers,

    Mario


[-- Attachment #2: configure.ac.patch --]
[-- Type: text/plain, Size: 873 bytes --]

--- gdb-6.8/configure.ac	2008-03-27 19:27:19.000000000 +0100
+++ /tmp/configure.ac	2008-08-16 17:50:22.000000000 +0200
@@ -1632,8 +1632,14 @@
   # Okay, some application will build, or we don't care to check.  Still
   # notify of subdirs not getting built.
   echo "*** This configuration is not supported in the following subdirectories:" 1>&2
-  echo "    ${notsupp}" 1>&2
-  echo "    (Any other directories should still work fine.)" 1>&2
+  echo "     ${notsupp}" 1>&2
+  if echo " ${notsupp} " | grep " gdb " >/dev/null 2>&1; then
+    echo "    which means gdb will not be built on this platform!" 1>&2
+    echo "    Continuing, though possible, is most likely not what you want." 1>&2
+    echo "    (However other directories should still work fine.)" 1>&2
+  else
+    echo "    (Any other directories should still work fine.)" 1>&2
+  fi
 fi
 
 case "$host" in

  reply	other threads:[~2008-08-16 15:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-16 16:11 Mario Emmenlauer
2008-08-16 17:37 ` Daniel Jacobowitz
2008-08-16 22:07   ` Mario Emmenlauer [this message]
2008-08-17 12:32     ` Stan Shebs
2008-08-16 17:51 ` Stan Shebs
2008-08-16 21:59 ` Dr. Rolf Jansen
2008-08-16 23:27   ` Mario Emmenlauer
     [not found]     ` <70C46A91-B195-4AAA-9EB9-7D97B93A4519@surtec.com>
2008-08-17 14:56       ` Mario Emmenlauer
2008-08-16 23:40   ` Stan Shebs
2008-08-17 14:54     ` Mario Emmenlauer
2008-08-17 17:00       ` Stan Shebs
2008-08-17 22:57         ` Robert Dewar
2008-08-18 10:21           ` Mario Emmenlauer
2008-08-18 12:42             ` Robert Dewar
2008-08-18 17:52           ` Stan Shebs
2008-08-18 17:55             ` Robert Dewar
2008-08-18 22:15     ` Michael Snyder

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=48A6F7D2.1080601@emmenlauer.de \
    --to=mario@emmenlauer.de \
    --cc=gdb@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox