Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: <gdb-patches@sourceware.org>
Subject: RE: [RFA v3] Allow cygwin native to compile with 	--enable-64-bit-bfd
Date: Thu, 06 Dec 2007 14:06:00 -0000	[thread overview]
Message-ID: <000f01c837fa$13661cf0$3a3256d0$@u-strasbg.fr> (raw)
In-Reply-To: <20071206043523.GA5142@ednor.casa.cgf.cx>

> >> > >2007-11-28  Pierre Muller  <muller@ics.u-strasbg.fr>
> >> > >
> >> > >	*win32-nat.c: Allow compilation if CORE_ADDR is 8 byte
> long.
> >> > >	Add "gdb_stdint.h" dependency required for uintptr_t type
> use.
> >>
> >> Added includes -> update Makefile.in.  Tom's been working on
> automatic
> >> dependencies for GCC.  Maybe we can do something similar for GDB
> >> soon...
> >
> > I modified the patch to add the change to Makefile.in.
> >
> >
> >  After checking again that there was
> >no change to the testsuite.
> >
> >OK to commit?
> 
> Ok.

Thanks, I just commit this,
after verifying that you can now create a cygwin gdb
with "--enable-targets=all --enable-64bit-bfd"
configure options.

Pierre Muller





      reply	other threads:[~2007-12-06 11:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-23  8:50 [RFC/RFA] " Pierre Muller
2007-11-24 21:07 ` Christopher Faylor
2007-11-24 22:47   ` Daniel Jacobowitz
2007-11-25 17:32     ` Christopher Faylor
2007-11-25 19:08       ` Daniel Jacobowitz
2007-11-25 22:12         ` Christopher Faylor
2007-11-26  9:12           ` Pierre Muller
2007-11-26 15:18             ` Ulrich Weigand
2007-11-29 10:11           ` [RFA v2] " Pierre Muller
2007-12-02  2:43             ` Christopher Faylor
2007-12-02  4:00               ` Daniel Jacobowitz
2007-12-03 15:18                 ` [RFA v3] " Pierre Muller
2007-12-06  9:23                   ` Christopher Faylor
2007-12-06 14:06                     ` Pierre Muller [this message]

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='000f01c837fa$13661cf0$3a3256d0$@u-strasbg.fr' \
    --to=muller@ics.u-strasbg.fr \
    --cc=gdb-patches@sourceware.org \
    /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