public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Chris.Pedley@arm.com
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: Cross Compiling GDB
Date: Wed, 20 Aug 2003 13:28:00 -0000	[thread overview]
Message-ID: <OF5D3FBB65.4D1C1395-ON80256D88.00486E86-80256D88.0049FF4A@cambridge.arm.com> (raw)


On 20/08/2003 14:05:30 gdb-owner wrote:
>On Wed, Aug 20, 2003 at 10:20:47AM +0100, Chris.Pedley@arm.com wrote:
>> I presume that the GDB at the following location isn't cygwin specific?
>> ftp.gnu.org/gnu/gdb/gdb-5.3.tar.gz
>>
>> However, if you look at line 53 in gdb-5.3/readline/configure.in then
>> it issues the error given above if cross compiling for a non-cygwin
>> target.
>>
>> Also my questions about build, host and target have been raised
>> because I'm unsure about the check for a cross compiler at line 123
>> in gdb-5.3/configure.in.  This checks whether the host and target
>> are the same thing, and only assumes it is a cross compiler if they
>> are different.  Why isn't this actually checking build and host?
>
>Can you be a little clearer what you're trying to do?
>
>First of all, that seems like a really lame bug in readline.  But it's
>easily fixable.  But second, do you want a cross debugger or a native
>debugger for a non-cygwin host?  $is_cross_compiler is whether the GCC
>being built will be a cross compiler - that configure script is shared
>with GDB.  That's a host vs target issue.

So is it definitely a bug, and is it definitely possible to cross compile
gdb
for other systems than cygwin?

I'm trying to build a gdb debugger to be run on ARM Linux to debug apps
natively running under ARM Linux.  I will be building gdb using the
arm-linux-gcc cross compiler on an Intel box, so was trying to configure
with:
target=arm-linux
build=i386-linux
host=arm-linux
with-headers=<path to kernel sources>/linux-2.4.19/include

This will fail because it will report that with-headers is only supported
when cross compiling.  I'm muddled as to what target, build and host
therefore actually are?

--
Chris Pedley,  Graduate Engineer
Intellectual Property Solutions Division
ARM Ltd, 110 Fulbourn Rd, Cambridge CB1 9NJ UK
Tel : +44 1223 400847     Fax: +44 1223 400410


             reply	other threads:[~2003-08-20 13:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-20 13:28 Chris.Pedley [this message]
2003-08-20 13:33 ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2003-08-20 14:17 Chris.Pedley
2003-08-20 14:24 ` Daniel Jacobowitz
2003-08-20  9:21 Chris.Pedley
2003-08-20 13:05 ` Daniel Jacobowitz
2003-08-19 17:40 Chris.Pedley
2003-08-19 17:43 ` Daniel Jacobowitz
2003-08-19 18:00   ` Christopher Faylor
2003-08-19 18:31     ` Daniel Jacobowitz
2003-08-19 20:56       ` Christopher Faylor

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=OF5D3FBB65.4D1C1395-ON80256D88.00486E86-80256D88.0049FF4A@cambridge.arm.com \
    --to=chris.pedley@arm.com \
    --cc=drow@mvista.com \
    --cc=gdb@sources.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).