From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: muller@ics.u-strasbg.fr (Pierre Muller), gdb-patches@sourceware.org
Subject: Re: [rfc] [0/9] Multi-target support
Date: Tue, 20 Nov 2007 22:17:00 -0000 [thread overview]
Message-ID: <200711202217.lAKMHCJs011064@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20071119172751.GA9441@caradoc.them.org> from "Daniel Jacobowitz" at Nov 19, 2007 12:27:51 PM
Daniel Jacobowitz wrote:
> On Mon, Nov 19, 2007 at 06:24:24PM +0100, Ulrich Weigand wrote:
> > > Adding --enable-64-bit-bfd I still needed to add WERROR_CFLAGS=""
> > > because I got warnings in win32-nat.c, which implicitly assumes that
> > > CORE_ADDR is 32 bit long.
> >
> > Now this is a bug in win32-nat.c, which would have already shown up
> > if you attempted to build a regular win32 -> amd64-linux (for example)
> > cross-debugger.
>
> Well, no - you wouldn't get win32-nat.c in that case. It would show
> up if you build a native Windows GDB with --enable-64-bit-bfd though.
You're right, of course. Sorry for the confusion.
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-20 22:17 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
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 [this message]
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=200711202217.lAKMHCJs011064@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=drow@false.org \
--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