From: Daniel Jacobowitz <drow@mvista.com>
To: Chris.Pedley@arm.com
Cc: Izo <I@siol.net>, gdb@sources.redhat.com
Subject: Re: Cross Compiling GDB
Date: Wed, 20 Aug 2003 14:24:00 -0000 [thread overview]
Message-ID: <20030820142453.GA10775@nevyn.them.org> (raw)
In-Reply-To: <OFD56586C6.A6C91DA0-ON80256D88.004D8104-80256D88.004E7735@cambridge.arm.com>
On Wed, Aug 20, 2003 at 03:17:02PM +0100, Chris.Pedley@arm.com wrote:
>
> On 20/08/2003 15:03:16 Izo wrote:
> >Chris.Pedley@arm.com wrote:
> >>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
> >>
> >>
> >
> >So you are building the gdb with the ix86 machine - so
> >host="i386-linux", or better (if you are using PIV - host="i686-linux")
> >So you are building for the arm target ==> target="arm-linux"
> >So the build is (amongst other builds) build="arm-linux"
> >
> >configure --prefix=whatever --host="i686-linux" --target="arm-linux"
> >--build="arm-linux"
> >
> >Consider using the export CFLAGS/CXXFLAGS="-fsigned-char -mcpu=one of
> >the arm ones -march=right one" prior to running configure to get the
> >properly working and optimized code for your target. Especially the
> >-fsigned-char (see the newest DrDobbsJournal for other ARM
> >compatibility/portability issues)
> >
>
> So you think host should be i386-linux, but the previous email in this
> thread suggests that Daniel Jacobowitz gets it to build with the host
> as arm-linux. Can someone please give me a definition of, or
> the document that defines the meaning of host, target and build?
The confusion is because you didn't specify clearly which kind of
debugger you wanted. You want a native debugger, not a cross debugger,
so you want host=arm-linux.
build: where you are building
host: where the result will run
target: the kind of binaries it will be able to debug/compile/whatever.
only applicable to tools like gcc and gdb. For instance, you
never build glibc with --target.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-08-20 14:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 14:17 Chris.Pedley
2003-08-20 14:24 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-20 13:28 Chris.Pedley
2003-08-20 13:33 ` 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=20030820142453.GA10775@nevyn.them.org \
--to=drow@mvista.com \
--cc=Chris.Pedley@arm.com \
--cc=I@siol.net \
--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).