From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com
Cc: drow@mvista.com, gdb@sources.redhat.com
Subject: Re: error building gcc , (simulators and targets...)
Date: Wed, 15 Jan 2003 17:13:00 -0000 [thread overview]
Message-ID: <200301151713.h0FHDXJ27116@duracef.shout.net> (raw)
It is happening to multiple people. It also happened to Johan Vermeire
as well (PR gdb/915). Johan also got stuck because his MS Win2K + IE
6.0 browser couldn't file a bug report, and then nobody looked at his
mail to gdb-bug@gnu.org.
Preventing PR's with better doco is a good thing, both for the users
and for us.
Better doco will help our direct users, and then our channel partners,
partners, the cross-gcc FAQ people, can uptake our new doco or refer to
it in their doco. That part won't happen overnight. The most recent
cross-gcc FAQ I've seen is from 1999!
(Honestly, I think gdb could benefit from lots of re-engineering for
our customer-facing business processes, I'm reading a Patricia Seybold
book and all this goobledygook actually does apply to the gdb project,
in my mind at least).
So I'll write that doco and submit it soon.
Michael C
next reply other threads:[~2003-01-15 17:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 17:13 Michael Elizabeth Chastain [this message]
2003-01-16 9:58 ` msarasa
2003-01-16 12:54 ` msarasa
2003-01-16 13:50 ` Daniel Jacobowitz
2003-01-16 14:18 ` msarasa
2003-01-16 14:31 ` Daniel Jacobowitz
2003-01-16 15:20 ` msarasa
-- strict thread matches above, loose matches on Subject: below --
2003-01-16 17:02 Michael Elizabeth Chastain
2003-01-15 16:50 Michael Elizabeth Chastain
2003-01-15 16:59 ` Andrew Cagney
2003-01-15 17:11 ` msarasa
2003-01-15 16:50 Daniel Jacobowitz
2003-01-15 16:48 Michael Elizabeth Chastain
2003-01-15 10:13 msarasa
2003-01-15 13:21 ` Daniel Jacobowitz
2003-01-15 16:13 ` Andrew Cagney
2003-01-15 16:15 ` Daniel Jacobowitz
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=200301151713.h0FHDXJ27116@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
/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