From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: muller@ics.u-strasbg.fr (Pierre Muller)
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] [0/9] Multi-target support
Date: Mon, 19 Nov 2007 11:38:00 -0000 [thread overview]
Message-ID: <200711191138.lAJBc20Z024695@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <003a01c82a95$07659290$1630b7b0$@u-strasbg.fr> from "Pierre Muller" at Nov 19, 2007 11:14:54 AM
Pierre Muller wrote:
> Is the CORE_ADDR size changed according to the target of the current tdep
> file?
CORE_ADDR is defined as bfd_vma, and the latter is supposed to be chosen
according to the selected targets (see the generated bfd/bfd.h file):
/* The word size used by BFD on the host. This may be 64 with a 32
bit target if the host is 64 bit, or if other 64 bit targets have
been selected with --enable-targets, or if --enable-64-bit-bfd. */
#define BFD_ARCH_SIZE 64
Not sure why this didn't work for you ... Did you start from a clean
build directory? Could you try whether at least explicitly specifying
--enable-64-bit-bfd works?
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2007-11-19 11:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 1:15 Ulrich Weigand
2007-10-26 7:19 ` Daniel Jacobowitz
2007-10-30 21:54 ` [rfc] [0/9] Multi-target support: Fix show_mipsfpu_command crash Ulrich Weigand
2007-11-17 1:08 ` [rfc] [0/9] Multi-target support Ulrich Weigand
2007-11-19 10:14 ` Pierre Muller
2007-11-19 11:38 ` Ulrich Weigand [this message]
2007-11-19 16:35 ` Pierre Muller
2007-11-19 17:24 ` Ulrich Weigand
2007-11-19 17:28 ` Daniel Jacobowitz
2007-11-20 22:17 ` Ulrich Weigand
2007-11-20 22:23 ` [rfc/rft] --enable-targets=all with 32-bit BFD Ulrich Weigand
2007-11-21 1:01 ` Pedro Alves
2007-11-26 15:30 ` Ulrich Weigand
2007-11-27 3:00 ` Pedro Alves
2007-11-27 17:08 ` Ulrich Weigand
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=200711191138.lAJBc20Z024695@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/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