From: Daniel Jacobowitz <drow@mvista.com>
To: Chris.Pedley@arm.com
Cc: gdb@sources.redhat.com
Subject: Re: Cross Compiling GDB
Date: Wed, 20 Aug 2003 13:05:00 -0000 [thread overview]
Message-ID: <20030820130530.GA8081@nevyn.them.org> (raw)
In-Reply-To: <OFAA40B82A.C4DA0D7A-ON80256D88.0032399F-80256D88.003357BA@cambridge.arm.com>
On Wed, Aug 20, 2003 at 10:20:47AM +0100, Chris.Pedley@arm.com wrote:
>
> On 19/08/2003 19:31:05 gdb-owner wrote:
> >On Tue, Aug 19, 2003 at 02:00:37PM -0400, Christopher Faylor wrote:
> >> On Tue, Aug 19, 2003 at 01:43:05PM -0400, Daniel Jacobowitz wrote:
> >> >On Tue, Aug 19, 2003 at 06:40:12PM +0100, Chris.Pedley@arm.com wrote:
> >> >>Is it actually possible to cross compile GDB for anything other than
> >> >>cygwin. In the output from ./configure when trying to configure for
> >> >>cross compiling using the GNU ARM tools I get the message: configure:
> >> >>cross-compiling for a non-cygwin target is not supported
> >> >>
> >> >>Also, can anyone confirm to me what the exact definitions of host,
> >> >>target and build are when passed to ./configure?
> >> >>
> >> >>Thanks.
> >> >
> >> >It sounds like you're using the Cygwin sources for GDB. If you're not
> >> >building a Cygwin-targeted GDB, don't do that - or direct comments to
> >> >the cygwin list.
> >>
> >> "Cygwin sources for gdb"? The sources for cygwin's gdb are the same as
> >> for any other platform.
> >
> >If so I apologize, but I swear I've heard of local patches from the
> >cygwin people before. Maybe I was thinking of another tool?
> >
> >In any case, that error message doesn't come from the FSF sources
> >anywhere.
> >
> >--
> >Daniel Jacobowitz
> >MontaVista Software Debian GNU/Linux Developer
>
> 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.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-08-20 13:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 9:21 Chris.Pedley
2003-08-20 13:05 ` Daniel Jacobowitz [this message]
-- 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 13:28 Chris.Pedley
2003-08-20 13:33 ` 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=20030820130530.GA8081@nevyn.them.org \
--to=drow@mvista.com \
--cc=Chris.Pedley@arm.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).