public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Ralf Corsepius <ralf.corsepius@rtems.org>,
	drow@false.org, 	gdb@sourceware.org, chrisj@rtems.org,
	joel.sherrill@OARcorp.com
Subject: Re: [ANNOUNCEMENT] GDB 6.7 released!
Date: Fri, 12 Oct 2007 16:42:00 -0000	[thread overview]
Message-ID: <20071012164237.GG4044@adacore.com> (raw)
In-Reply-To: <uzlyol2d7.fsf@gnu.org>

> > I encountered this issue when building gdb-4.7 rpms from original
> > gdb-6.7 tarballs with no patches applied.
> 
> Sorry, I don't understand: are you saying that you don't see the
> *.info* files in the gdb-6.7 tarball (some or all of them)?

For the record, here is the list of info files that I am seeing
in the gdb-6.7 tarball:

bfd/doc/bfd.info       gdb/doc/gdb.info-1   gdb/doc/gdbint.info-1
etc/configure.info     gdb/doc/gdb.info-2   gdb/doc/gdbint.info-2
etc/standards.info     gdb/doc/gdb.info-3   gdb/doc/stabs.info
gdb/doc/annotate.info  gdb/doc/gdb.info-4
gdb/doc/gdb.info       gdb/doc/gdbint.info

-- 
Joel

  reply	other threads:[~2007-10-12 16:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-10 19:19 Joel Brobecker
2007-10-11 11:49 ` Ralf Corsepius
2007-10-11 12:14   ` Daniel Jacobowitz
2007-10-11 13:54     ` Ralf Corsepius
2007-10-11 14:04       ` Daniel Jacobowitz
2007-10-11 15:52         ` Joel Brobecker
2007-10-12 14:04           ` Daniel Jacobowitz
2007-10-12  8:01       ` Eli Zaretskii
2007-10-12  9:15         ` Ralf Corsepius
2007-10-12 16:34           ` Eli Zaretskii
2007-10-12 16:42             ` Joel Brobecker [this message]
2007-10-14  9:46             ` Ralf Corsepius
2007-10-14 15:39               ` Daniel Jacobowitz
2007-10-14 20:38                 ` Eli Zaretskii
2007-10-14 20:57                   ` Daniel Jacobowitz
2007-10-14 20:27               ` Eli Zaretskii
2007-10-13  4:15 Michael Snyder

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=20071012164237.GG4044@adacore.com \
    --to=brobecker@adacore.com \
    --cc=chrisj@rtems.org \
    --cc=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=joel.sherrill@OARcorp.com \
    --cc=ralf.corsepius@rtems.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).