From: Guenther Grau <Guenther.Grau@bk.bosch.de>
To: gdb@cygnus.com
Subject: Re: gdb-19990209 on sparc-2.5.1
Date: Thu, 01 Apr 1999 00:00:00 -0000 [thread overview]
Message-ID: <36FB482C.FB91C76@bk.bosch.de> (raw)
In-Reply-To: <199903252355.PAA05700@andros.cygnus.com>
Stan Shebs wrote:
>
> Date: Thu, 25 Mar 1999 23:37:44 +0100
> From: Guenther Grau <Guenther.Grau@bk.bosch.de>
>
> Stan Shebs wrote:
> > No. 4.17.86 is similar to 19990209, but comes from a branch that was
> > sprouted from the trunk on 15 Feb, and includes a bunch of little
> > fixes that were done as part of the pre-release testing process.
> > 19990209 is derived from the repository trunk by whacking out
> > Cygnus-only bits. You should see fewer problems with 4.17.86.
> [...]
> > Try 4.17.86 instead - I remember something about a configuration
> > problem in opcodes in a snapshot, that might be the one.
>
> Ok. I did that, and it does indeed build properly. The warnings
> are still there, though. Do you accept any patches fixing the
> warnings?
>
> Sure, but not for 4.18, it's time to get it into users' hands.
>
> Fortunately, this isn't going to be the last GDB release ever :-), so
> it's still worthwhile to make all the warnings go away. Andrew C.
> has been bashing many of them, but there are lots left...
That's fine with me. I prefer a clear statement as to when things
are wellcome, and when not. I'll see what I can do for the first
snapshot after 4.18.
On the way of leaveing my office ...
Guenther
next parent reply other threads:[~1999-04-01 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199903252355.PAA05700@andros.cygnus.com>
1999-04-01 0:00 ` Guenther Grau [this message]
1999-04-01 0:00 4.17.86 on AIX 4.2.0.0 using IBM xlc Stan Shebs
1999-04-01 0:00 ` gdb-19990209 on sparc-2.5.1 Guenther Grau
1999-04-01 0:00 ` Stan Shebs
1999-04-01 0:00 ` Guenther Grau
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=36FB482C.FB91C76@bk.bosch.de \
--to=guenther.grau@bk.bosch.de \
--cc=gdb@cygnus.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