public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: Building GDB 7.3.92 with MinGW
Date: Tue, 10 Jan 2012 19:25:00 -0000	[thread overview]
Message-ID: <m3k44zid81.fsf@fleche.redhat.com> (raw)
In-Reply-To: <83hb03e9sx.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 10 Jan	2012 19:39:42 +0200")

>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:

Eli>   Any objections to the following patch?  (If approved, I will add a
Eli>   comment explaining the problem on Windows which requires this.)
Eli>      --- gdb/gdb_curses.h~0	2012-01-06 06:43:14.000000000 +0200
Eli>      +++ gdb/gdb_curses.h	2012-01-10 13:21:10.626119900 +0200
Eli>      @@ -27,6 +27,9 @@
Eli>       #elif defined (HAVE_CURSESX_H)
Eli>       #include <cursesX.h>
Eli>       #elif defined (HAVE_CURSES_H)
Eli>      +#if defined(__MINGW32__) && defined(MOUSE_MOVED)
Eli>      +#undef MOUSE_MOVED
Eli>      +#endif
Eli>       #include <curses.h>
Eli>       #endif

I don't really mind this patch.  But, why is this something for gdb to
solve rather than mingw?

Eli> 2. "make install-strip" fails in readline/, in sim/, and in gdb/:

Eli>    The reason is that these directories simply don't have the
Eli>    "install-strip" target in their Makefile.in files.  I think that
Eli>    target should be added, because that's AFAIK how GDB is supposed to
Eli>    be installed on end-user systems.

This is in the GNU standards, but in practice few people use it.

Of course, patches are welcome.  This isn't the only places where gdb's
Makefiles diverge from the standards.

Eli> 3. Manuals are (unexpectedly) regenerated as part of "make":

Eli>    I think these two files should be added to the distribution, since
Eli>    end users should not be required to have Texinfo installed to build
Eli>    GDB.

No opinion on this one.

Eli> Finally, a question: Why are we installing libraries (libbfd,
Eli> libopcodes, libiberty) and the standards.info manual?  The libraries
Eli> are not part of GDB, we import them from elsewhere.  "make install"
Eli> will happily overwrite existing installation of these libraries that
Eli> could potentially be newer, coming from their respective upstream
Eli> distributions.  How about removing these from "make install"?

For libiberty, gcc is the authoritative source.  So, ask there.

For the others, ask on the binutils list.

I tend to agree they should not be installed.

Eli> As for standards.info, if we decide to keep distributing it (which I
Eli> don't think we should), we should at least make a point of having the
Eli> latest version in our tarballs; the one in 7.3.92 isn't.

IMO we should remove this.  Actually, most of the things in src/etc seem
outdated or useless or somebody else's code.

I'm not sure who owns this directory, you should ask on binutils before
taking any action.

Tom

  parent reply	other threads:[~2012-01-10 19:12 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10 18:46 Eli Zaretskii
2012-01-10 18:59 ` Doug Evans
2012-01-10 20:56   ` Eli Zaretskii
2012-01-13 11:28   ` Eli Zaretskii
2012-01-10 19:25 ` Tom Tromey [this message]
2012-01-10 20:55   ` Joseph S. Myers
2012-01-10 20:58   ` Eli Zaretskii
2012-01-10 21:00   ` Eli Zaretskii
2012-01-10 19:31 ` Alfred M. Szmidt
2012-01-10 21:01   ` Eli Zaretskii
2012-01-10 21:26     ` Doug Evans
2012-01-11  0:37       ` asmwarrior
2012-01-11  4:08         ` Eli Zaretskii
2012-01-11  4:54           ` asmwarrior
2012-01-11 17:54         ` Doug Evans
2012-01-12  0:17           ` asmwarrior
2012-01-12  6:47             ` Eli Zaretskii
2012-01-12  8:07               ` Joel Brobecker
2012-01-12 11:54                 ` Eli Zaretskii
2012-01-12 12:35                   ` Joel Brobecker
2012-01-12 16:59                     ` Eli Zaretskii
2012-01-13 14:29                       ` asmwarrior
2012-01-13 16:55                         ` Eli Zaretskii
2012-01-14 13:53                           ` asmwarrior
     [not found]                           ` <4F117B33.8080906@gmail.com>
2012-01-14 18:15                             ` Eli Zaretskii
2012-01-15  3:33                               ` Pierre Muller
     [not found]                               ` <18546.4176851839$1326580387@news.gmane.org>
2012-01-15  3:54                                 ` asmwarrior
     [not found]                               ` <000001ccd30c$5ce854e0$16b8fea0$%muller@ics-cnrs.unistra.fr>
2012-01-15 13:35                                 ` Eli Zaretskii
2012-01-15 17:01                                   ` Joel Brobecker
2012-01-15 18:55                                     ` Eli Zaretskii
2012-01-15 18:01                                   ` Pierre Muller
     [not found]                                   ` <000301ccd3a7$3db8c460$b92a4d20$%muller@ics-cnrs.unistra.fr>
2012-01-15 18:55                                     ` Eli Zaretskii
2012-01-16  3:08                                       ` Pierre Muller
2012-01-10 21:33     ` Tom Tromey
2012-01-11  1:31       ` asmwarrior
2012-01-11  4:30         ` Eli Zaretskii
2012-01-11  4:30           ` asmwarrior
2012-01-11  3:32 ` Joel Brobecker
2012-01-13 11:06   ` Eli Zaretskii
2012-01-13 12:39     ` Joel Brobecker
2012-01-13 13:56       ` Eli Zaretskii

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=m3k44zid81.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=eliz@gnu.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).