Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Tristan Gingold <gingold@adacore.com>, Peter Steiner <sp@med-2-med.com>
Subject: Re: gdb darwin target on Linux host?
Date: Wed, 20 Oct 2010 14:26:00 -0000	[thread overview]
Message-ID: <201010201526.23403.pedro@codesourcery.com> (raw)
In-Reply-To: <455D00D6-4418-4B70-808B-37A9810F4F43@adacore.com>

On Wednesday 20 October 2010 15:20:49, Tristan Gingold wrote:
> 
> On Oct 20, 2010, at 3:52 PM, Peter Steiner wrote:
> 
> > Hi
> > 
> > I try to compile a darwin-target gdb running on a Linux host:
> > 
> > ./configure --prefix=/usr/local/gdb --target=x86_64-darwin
> > 
> > this works up to the end of configure & make however does NOT generate a
> > gdb binary! After make install the bin directory is empty and NO gdb
> > binary has been linked at all.
> > 
> > if I do:
> > 
> > ./configure --prefix=/usr/local/gdb --target=i386-darwin
> > 
> > this creates a gdb binary however it cannot read 64bit binaries from
> > darwin. Any idea what is wrong?
> 
> Could you post the log messages ?  I suppose that if no binary is built, then an error has occurred.
> 
> Not sure why you try to build such a tool, as it would be basically useless to debug.
> 
> 

Apparently, the top-level configure is finicky about darwin versions:

  i[[3456789]]86-*-darwin*)
    noconfigdirs="$noconfigdirs ld gprof"
    noconfigdirs="$noconfigdirs sim target-rda"
    ;;
  x86_64-*-darwin[[912]]*)
    noconfigdirs="$noconfigdirs ld gas gprof"
    noconfigdirs="$noconfigdirs sim target-rda"
    ;;
  *-*-darwin*)
    noconfigdirs="$noconfigdirs ld gas gdb gprof"
                                       ^^^
    noconfigdirs="$noconfigdirs sim target-rda"
    noconfigdirs="$noconfigdirs ${libgcj}"
    ;;


Something like "--target=x86_64-darwin10" instead works, and
I suppose "--target=i386-darwin --enable-64-bit-bfd" would
solve the OPs second attempt.

-- 
Pedro Alves


  reply	other threads:[~2010-10-20 14:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-20 13:53 Peter Steiner
2010-10-20 14:20 ` Tristan Gingold
2010-10-20 14:26   ` Pedro Alves [this message]
2010-10-20 14:41     ` Tristan Gingold
2010-10-20 14:50       ` Pedro Alves
2010-10-20 14:52         ` Nathan Froyd
2010-10-20 15:09           ` Pedro Alves
     [not found]           ` <20101020150949.4841131366@nx.neverkill.us>
2010-10-20 15:15             ` Peter Steiner
     [not found] ` <20101020143016.6BE9131366@nx.neverkill.us>
2010-10-20 14:42   ` Peter Steiner
2010-10-20 15:12     ` Tristan Gingold
     [not found]     ` <20101020151257.25F2D31366@nx.neverkill.us>
2010-10-20 15:24       ` Peter Steiner
2010-10-20 17:12         ` Stan Shebs
2010-10-21  7:49           ` Tristan Gingold
2010-10-20 15:35       ` Peter Steiner
     [not found]       ` <1287588922.28107.281.camel@hp>
2010-10-20 15:45         ` Paul Starzetz

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=201010201526.23403.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb@sourceware.org \
    --cc=gingold@adacore.com \
    --cc=sp@med-2-med.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