Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org, toolchain-devel@blackfin.uclinux.org
Subject: Re: [PATCH] sim: generate build dependencies on the fly
Date: Wed, 13 Jul 2011 13:59:00 -0000	[thread overview]
Message-ID: <m3d3hee2p7.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CAJaTeTpoc=UUiePTTBNiRA=dREKdYABMfXQ+HdCsDWaa4wuG0w__27433.0390304842$1310506984$gmane$org@mail.gmail.com>	(Mike Frysinger's message of "Tue, 12 Jul 2011 17:42:10 -0400")

>>>>> "Mike" == Mike Frysinger <vapier@gentoo.org> writes:

Mike> but would saying "yes, this works on current BSD makes" be
Mike> satisfactory when the complaint in the manual alludes to "ancient
Mike> makes" ?

It would be a good start.

A general problem in gdb is that we aren't always aware of what hosts
users build on -- we can't distinguish "no report because it just kept
working" from "no report because there are no more users".

Joel builds on some odd hosts, maybe he could say what versions of make
he uses.  Likewise perhaps the Sourcerers.

Tom


  parent reply	other threads:[~2011-07-13 13:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1310436152-8693-1-git-send-email-vapier__46811.2245122485$1310436164$gmane$org@gentoo.org>
2011-07-12 19:49 ` Tom Tromey
2011-07-12 20:59   ` Mike Frysinger
     [not found]   ` <CAJaTeTqM-Kr3Nrr4JKyfpys7=+aWk_YJCA+=AensJyBTUvg4dQ__24418.5384632603$1310503395$gmane$org@mail.gmail.com>
2011-07-12 21:15     ` Tom Tromey
2011-07-13  2:04       ` Mike Frysinger
     [not found]       ` <CAJaTeTpoc=UUiePTTBNiRA=dREKdYABMfXQ+HdCsDWaa4wuG0w__27433.0390304842$1310506984$gmane$org@mail.gmail.com>
2011-07-13 13:59         ` Tom Tromey [this message]
2011-07-13 20:17           ` Mike Frysinger
2011-07-12  5:18 Mike Frysinger
2011-12-03 18:24 ` Mike Frysinger

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=m3d3hee2p7.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=toolchain-devel@blackfin.uclinux.org \
    --cc=vapier@gentoo.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